OWASP Top 10 2025 Training Course

A01:2025 - Broken Access Control
A02:2025 - Security Misconfiguration
A03:2025 - Software Supply Chain Failures
A04:2025 - Cryptographic Failures
A05:2025 - Injection
A06:2025 - Insecure Design
A07:2025 - Authentication Failures
A08:2025 - Software or Data Integrity Failures
A09:2025 - Security Logging and Alerting Failures
A10:2025 - Mishandling of Exceptional Conditions

A01:2025 Broken Access Control - Access control mechanisms enforce policies ensuring users cannot act beyond their intended permissions. Failures in this area often result in unauthorized disclosure, modification, or destruction of data, or the execution of business functions outside of authorized limits.

A02:2025 Security Misconfiguration - This occurs when a system, application, or cloud service is incorrectly set up from a security standpoint, thereby introducing vulnerabilities.

A03:2025 Software Supply Chain Failures - These refer to compromises or breakdowns in the processes of building, distributing, or updating software. Such failures are frequently caused by vulnerabilities or malicious alterations in third-party code, tools, or other dependencies relied upon by the system.

A04:2025 Cryptographic Failures - Generally, all data in transit should be encrypted at the transport layer (OSI layer 4). Previous challenges regarding CPU performance and private key/certificate management have been mitigated by modern CPUs with instructions designed to accelerate encryption (e.g., AES support) and simplified key management via services like LetsEncrypt.org, along with tightly integrated certificate management services provided by major cloud vendors. Beyond securing the transport layer, it is crucial to identify which data requires encryption at rest and which data needs additional encryption in transit (at the application layer, OSI layer 7). For instance, passwords, credit card numbers, health records, personal information, and business secrets demand extra protection, particularly when subject to privacy laws such as the EU's General Data Protection Regulation (GDPR) or regulations like the PCI Data Security Standard (PCI DSS).

A05:2025 Injection - An injection vulnerability is a system flaw that permits an attacker to insert malicious code or commands (such as SQL or shell code) into a program’s input fields, deceiving the system into executing them as if they were legitimate parts of the system. This can have severe consequences.

A06:2025 Insecure Design - Insecure design is a broad category encompassing various weaknesses, characterized as “missing or ineffective control design.” It is distinct from being the root source of all other Top Ten risk categories. Note the difference between insecure design and insecure implementation; we distinguish between design flaws and implementation defects because they have different root causes, occur at different stages of the development process, and require different remediation strategies. A secure design may still suffer from implementation defects that lead to exploitable vulnerabilities. Conversely, an insecure design cannot be resolved by perfect implementation if the necessary security controls were never initially designed to defend against specific attacks. A contributing factor to insecure design is often the lack of business risk profiling inherent in the software or system, leading to a failure to determine the required level of security design.

A07:2025 Authentication Failures - This vulnerability exists when an attacker can trick a system into recognizing an invalid or incorrect user as legitimate.

A08:2025 Software or Data Integrity Failures - These failures relate to code and infrastructure that fails to protect against invalid or untrusted code or data being treated as trusted and valid. An example is an application relying on plugins, libraries, or modules from untrusted sources, repositories, or content delivery networks (CDNs). An insecure CI/CD pipeline lacking software integrity checks can introduce risks of unauthorized access, insecure or malicious code, or system compromise. Another example is a CI/CD system that pulls code or artifacts from untrusted locations and/or does not verify them before use (e.g., by checking signatures or similar mechanisms).

A09:2025 Security Logging & Alerting Failures - Without logging and monitoring, attacks and breaches remain undetected, and without alerting, it becomes very difficult to respond quickly and effectively during a security incident. Insufficient logging, continuous monitoring, detection, and alerting to initiate active responses is a critical gap.

A10:2025 Mishandling of Exceptional Conditions - Mishandling exceptional conditions in software occurs when programs fail to prevent, detect, and respond to unusual and unpredictable situations, leading to crashes, unexpected behavior, and potential vulnerabilities. This can involve one or more of the following failings: the application does not prevent an unusual situation from happening, it does not identify the situation as it occurs, and/or it responds poorly or not at all to the situation afterwards.

We will discuss and present practical aspects of:

Broken Access Control
- Practical examples of broken access controls
- Secure access controls and best practices

Security Misconfiguration
- Real-world examples of misconfigurations
- Steps to prevent misconfiguration, including configuration management and automation tools

Cryptographic Failures
- Detailed analysis of cryptographic failures such as weak encryption algorithms or improper key management
- Importance of strong cryptographic mechanisms, secure protocols (SSL/TLS), and examples of modern cryptography in web security

Injection Attacks
- Detailed breakdown of SQL, NoSQL, OS, and LDAP injection
- Mitigation techniques using prepared statements, parameterized queries, and escaping inputs

Insecure Design
- We'll explore design flaws that can lead to vulnerabilities, like improper input validation
- We'll study strategies for secure architecture and secure design principles

Authentication Failures
- Common authentication issues
- Secure authentication strategies, like multi-factor authentication and proper session handling

Software and Data Integrity Failures
- Focus on issues like untrusted software updates and data tampering
- Safe update mechanisms and data integrity checks

Security Logging and Monitoring Failures
- Importance of logging security-relevant information and monitoring for suspicious activities
- Tools and practices for proper logging and real-time monitoring to detect breaches early