rebuild

Career/Concepts.md

@@ -65,7 +65,8 @@ Some core programming concepts that are essential for software development. The
 
 # Security:
 
-  - [[Cross Site Scripting (XSS)]]
+- [[OWASP Top 10]]
+- [[Cross Site Scripting (XSS)]]
 
 # Concepts to learn and talk about (cs and maths)
 

Career/Security/OWASP Top 10.md

@@ -0,0 +1,18 @@
+This stands for Open Web Application Security Project. 
+
+It is a non profit foundation which publishes the OWASP top 10, which is a standard document that identifies the most critical security risks to web applications.
+
+Current edition: **OWASP Top 10:2025**
+
+The 2025 list ranks risks as follows:
+
+- **A01:2025 Broken Access Control**: Remains the #1 risk, covering unauthorized access and privilege escalation; includes [[Server-Side Request Forgery (SSRF)]]. 
+- **A02:2025 Security Misconfiguration**: Moved up to #2, highlighting insecure defaults, exposed services, and inconsistent controls. 
+- **A03:2025 Software Supply Chain Failures**: A new, expanded category (from "Vulnerable and Outdated Components") covering dependencies, CI/CD systems, and distribution infrastructure. 
+- **A04:2025 Cryptographic Failures**: Covers insecure encryption, weak key management, and data exposure. 
+- **A05:2025 Injection**: Includes SQL, OS, and template injection flaws. 
+- **A06:2025 Insecure Design**: Focuses on architectural weaknesses and lack of threat modeling. 
+- **A07:2025 Authentication Failures**: Covers weak login flows, session handling, and password policies. 
+- **A08:2025 Software or Data Integrity Failures**: Addresses tampering with code, data, or CI/CD pipelines. 
+- **A09:2025 Security Logging & Alerting Failures**: Highlights gaps in monitoring that allow attacks to go undetected. 
+- **A10:2025 Mishandling of Exceptional Conditions**: A new category focusing on unsafe error handling and system resilience during failures.

Career/Security/Server-Side Request Forgery (SSRF).md

@@ -0,0 +1,17 @@
+This is a critical web security vulnerability where an attacker manipulates a server into making unauthorised HTTP requests to internal or external resources on the attacker's behalf.
+
+## How SSRF Attacks Work
+
+In a typical SSRF attack, the attacker manipulates input fields (such as URL parameters, form fields, or HTTP headers) that the server uses to initiate a request. Because the request originates from the trusted server itself, it often bypasses firewalls, VPNs, and network segmentation that would block direct external access. 
+
+### Common Attack Vectors
+
+- **Cloud Metadata Services:** Attackers often target cloud provider metadata endpoints (e.g., `http://169.254.169.254/` in AWS) to steal temporary credentials and configuration data. 
+    
+- **Internal Services:** Requests can be directed to internal administrative dashboards, databases with HTTP interfaces (like MongoDB or Redis), or other backend services lacking authentication. 
+    
+- **Local File System:** By using the `file://` protocol, attackers may attempt to read sensitive files on the server (e.g., `/etc/passwd`). 
+    
+- **Port Scanning:** SSRF can be used to scan internal networks for open ports and running services by observing response times or error messages.
+
+![[Pasted image 20260602161410.png]]