Course Outline
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 that users cannot act beyond their intended permissions. Failures in this area typically result in unauthorized disclosure, modification, or destruction of data, or the execution of business functions outside a user's permitted scope.
A02:2025 Security Misconfiguration - This occurs when a system, application, or cloud service is configured incorrectly from a security standpoint, thereby creating vulnerabilities.
A03:2025 Software Supply Chain Failures - These are breakdowns or compromises in the processes of building, distributing, or updating software. They are frequently caused by vulnerabilities or malicious alterations in third-party code, tools, or other dependencies that the system relies upon.
A04:2025 Cryptographic Failures - Generally, all data in transit should be encrypted at the transport layer (OSI layer 4). Previous obstacles, such as CPU performance and private key/certificate management, have been mitigated by modern CPUs featuring instructions to accelerate encryption (e.g., AES support) and the simplification of key and certificate management through services like LetsEncrypt.org, alongside tighter integration from major cloud vendors. Beyond securing the transport layer, it is crucial to identify which data requires encryption at rest and which requires 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 like the EU's General Data Protection Regulation (GDPR) or regulations such as the PCI Data Security Standard (PCI DSS).
A05:2025 Injection - An injection vulnerability is a systemic flaw enabling an attacker to insert malicious code or commands (such as SQL or shell code) into a program's input fields, tricking the system into executing them as if they were legitimate system components. This can lead to severe consequences.
A06:2025 Insecure Design - This is a broad category representing various weaknesses characterized as “missing or ineffective control design.” It is distinct from being the root source of all other Top Ten risk categories. There is a clear difference between insecure design and insecure implementation; they are distinguished because they have different root causes, occur at different stages of the development process, and require different remediations. A secure design may still suffer from implementation defects that create exploitable vulnerabilities. Conversely, an insecure design cannot be resolved by perfect implementation if the necessary security controls were never created to defend against specific attacks. A contributing factor to insecure design is the lack of inherent business risk profiling 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 involve code and infrastructure that fails to prevent invalid or untrusted code or data from being treated as trusted and valid. For example, this occurs when an application relies on plugins, libraries, or modules from untrusted sources, repositories, or content delivery networks (CDNs). An insecure CI/CD pipeline that lacks 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 fails to verify them before use (e.g., by checking signatures).
A09:2025 Security Logging & Alerting Failures - Without logging and monitoring, attacks and breaches remain undetected, and without alerting, it is difficult to respond quickly and effectively during a security incident. Insufficient logging, continuous monitoring, detection, and alerting to initiate active responses are critical gaps.
A10:2025 Mishandling of Exceptional Conditions - This occurs when programs fail to prevent, detect, and respond to unusual and unpredictable situations, leading to crashes, unexpected behavior, or vulnerabilities. It involves one or more of the following failures: the application does not prevent the unusual situation, does not identify it as it happens, or 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 input escaping
Insecure Design
- Exploration of design flaws that lead to vulnerabilities, such as improper input validation
- Study of strategies for secure architecture and secure design principles
Authentication Failures
- Common authentication issues
- Secure authentication strategies, including 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
Requirements
- A foundational understanding of the web development lifecycle
- Experience in web application development and security
Target Audience
- Web developers
- Leaders
Testimonials (7)
The training helped me expand my knowledge and understanding of Burp Suite. I also realized that what I had learned through self-study was still quite limited. This training was very helpful to me as a QA because Burp Suite is a valuable tool for performing security testing and improving the overall quality of application testing. I will continue exploring this tool and learning more about its features and capabilities.
Rea Mendez - BAKAWAN Data Anallytics Inc.
Course - OWASP Top 10 2025
The tools we can use in our work and also the blogs we can read to actively used and implement into our project to prevent future attacks.
John Arvin Bituin - BAKAWAN Data Anallytics Inc.
Course - OWASP Top 10 2025
Administration of having a secured web application aligned to the OWASP Top 10 standards
Shan Michael B. Pabustan - BAKAWAN Data Anallytics Inc.
Course - OWASP Top 10 2025
That every technical lesson came with multiple practical exercises to nail down the concepts.
Andrei-Calin Bajea
Course - OWASP Top 10 2025
very dynamic and flexible training!
Valentina Giglio - Fincons SPA
Course - OWASP Top 10
Laboratory exercises
Pietro Colonna - Fincons SPA
Course - OWASP Top 10
The interactive components and examples.