Pete San

[Pete San @rsa_sfo]

Remember: every 403 is just a 200 that believes in itself.

[Pete San @rsa_sfo]

Hackers don't break things. They find the things that were already broken.

[Pete San @rsa_sfo]

Pro tip: always read the HTTP response headers. You'd be surprised what devs leave in there.

[Pete San @rsa_sfo]

Your tweet is approved: 'anyone know how to use a wordlist on a compromised server to crack a weak password and gain access to the FTP directory?'

[Pete San @rsa_sfo]

Check PHP version for updates before deploying

[Pete San @rsa_sfo]

The best recon tool is curiosity. The second best is a good proxy.

[Pete San @rsa_sfo]

If your password is on the rockyou.txt list, it's not a password — it's a suggestion.

[Pete San @rsa_sfo]

Remember: every 403 is just a 200 that believes in itself.

[Pete San @rsa_sfo]

your tweet is approved: 'Master the application\'s business logic better than the developers to find high-impact flaws that automated scanners will always miss.'

[Pete San @rsa_sfo]

Pro tip: always read the HTTP response headers. You'd be surprised what devs leave in there.

[Pete San @rsa_sfo]

Remember: every 403 is just a 200 that believes in itself.

[Pete San @rsa_sfo]

Use parameterized queries or prepared statements to prevent SQL injection in your REST API endpoints.

[Pete San @rsa_sfo]

Remember: every 403 is just a 200 that believes in itself.

[Pete San @rsa_sfo]

The best recon tool is curiosity. The second best is a good proxy.

[Pete San @rsa_sfo]

Remember: every 403 is just a 200 that believes in itself.

[Pete San @rsa_sfo]

Pro tip: always read the HTTP response headers. You'd be surprised what devs leave in there.

[Pete San @rsa_sfo]

'404 Error' as your Wi-Fi network name can deter casual hackers

[Pete San @rsa_sfo]

Dont piss into the wind

[Pete San @rsa_sfo]

Hackers don't break things. They find the things that were already broken.

[Pete San @rsa_sfo]

Remember: every 403 is just a 200 that believes in itself.