3 ms·
> To make sure this doesn't happen again, OWASP said it disabled directory browsing and checked the web server for additional configuration and security issues,
by k12sosse 3y ago
> To make sure this doesn't happen again, OWASP said it disabled directory browsing and checked the web server for additional configuration and security issues, and removed all of the resumes from the site.
> Additionally, the foundation purged the CloudFlare caches, and requested that the accessed data be removed from the web archive.
If the attacker didn't break in but rather accessed public internet facing traffic is it really a breach? What was breached? The webserver? on port 80? [0]
[0] https://owasp.org/blog/2024/03/29/OWASP-data-breach-notification https://owasp.org/blog/2024/03/29/OWASP-data-breach-notifica...
- ripjaygn 3y agoThe resumes were not meant to be public. That's the data breach. How it happened is a mere detail. In this case it's directory browsing because of web server misconfiguration, a top 10 OWASP no-no. https://owasp.org/www-project-top-ten/2017/A6_2017-Security_Misconfiguration https://owasp.org/www-project-top-ten/2017/A6_2017-Security_... Check Scenario #2