Ess CYS · Group 1 · Class activity

Not Proof

Anonymity, proxies and antiforensics

Yasir Dhawi · Yousef Mohammed · Mohammed Al Abyah · Abdulaziz Alharthi

The motion

Defenders should prioritize detecting anonymization techniques over strengthening prevention controls.

Our vote is no. We still want to notice these tools. We just would not put that ahead of stopping the way in, keeping the logs, and being able to recover.

Three reasons

  1. 01Hiding is not how they get inA proxy, a tunnel, or deleted logs gives them time and makes it harder to say who did it. It does not get them in.
  2. 02A VPN is not proofYou can often see that someone used a proxy or a VPN. That does not mean they are the attacker. Staff and journalists use the same tools.
  3. 03A name does not fix itAfter the logs are gone, you can still cut the machine off and recover. Finding out who did it often takes too long.

The four questions

Each layer

A proxy chain hides where they are. A tunnel hides what they are sending. Deleting logs makes the investigation harder. None of that is how they got in.

Detection

Normal users, shared addresses, and an ordinary rented server all mean “this is a proxy” is a hint, not a verdict.

Restrict or monitor?

Journalists and dissidents use the same proxies and VPNs. Rules on your own computers are fair. Restricting the tools for everyone, or monitoring someone only because they used one, is not.

Attribution, or recovery?

Finding the name is worth it later, if the same people will come back and someone can use the name. Containment and recovery come first.

The three cases

A botnet, through proxy layers

Commands pass through more than one proxy. Blocking one address does not name who runs it, and it does not stop the botnet.

Logs that were wiped

The investigation opens and the log on that machine is gone. If that was the only copy, noticing the gap is already late.

Steganography

Stolen data leaves looking like a normal file. We would not try to recognise every hiding trick. We would limit who can open the data, and where it can go.

Where we would spend the money

  1. 1Stop the way inPasswords and MFA, updates, less access than people actually need, and rules for where machines can connect.
  2. 2Keep a copy of the logsSomewhere the hacked computer cannot delete.
  3. 3Practice the recoveryCut the machine off, change the passwords, and backups you have actually restored before.
  4. 4Notice the hidingOne hint, looked at by a person, next to something stronger.
  5. 5Find the nameOnly if they will come back and someone can use it.

Try it

This is a small page we made for the presentation. The site runs on Cloudflare Workers. Votes and questions sit in Turso. If you ask something, DeepSeek answers from what we said in class. It will not tell you how to hide traffic or delete logs.

Vote on the motion

We only keep the count, not your name.

Ask us