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 controls are mechanisms that enforce policies to ensure users cannot exceed their authorized permissions. Failures in this area often result in unauthorized disclosure, alteration, or destruction of data, as well as the execution of business functions beyond a user’s scope.
A02:2025 Security Misconfiguration - This occurs when systems, applications, or cloud services are not configured with security in mind, leaving them exposed to vulnerabilities.
A03:2025 Software Supply Chain Failures - These refer to compromises or failures in the software build, distribution, or update processes. They frequently stem from vulnerabilities or malicious modifications 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). Former obstacles such as CPU performance constraints and complex private key/certificate management are now mitigated by modern CPUs supporting accelerated encryption instructions (e.g., AES) and simplified management services like LetsEncrypt.org. Major cloud providers also offer deeply integrated certificate management for their platforms. Beyond transport layer security, it is crucial to identify data requiring encryption at rest and data needing additional application-layer (OSI layer 7) protection. Sensitive data such as passwords, credit card details, health records, personal information, and business secrets require robust safeguards, particularly when subject to privacy regulations like the EU’s GDPR or standards such as PCI DSS.
A05:2025 Injection - An injection vulnerability is a flaw that permits attackers to inject malicious code or commands (such as SQL or shell scripts) into input fields, causing the system to execute these as if they were legitimate internal operations. This can lead to severe consequences.
A06:2025 Insecure Design - Insecure design is a broad category encompassing various weaknesses, characterized by “missing or ineffective control design.” It is distinct from the source of other Top Ten risks. It is important to distinguish between design flaws and implementation defects, as they have different root causes, occur at different stages of development, and require different remediation approaches. A securely designed system may still suffer from implementation defects that create exploitable vulnerabilities. Conversely, an insecure design cannot be rectified by perfect implementation, as the necessary security controls were never established to defend against specific threats. A key contributor to insecure design is the absence of business risk profiling during the software or system development process, leading to an unclear understanding of the required security level.
A07:2025 Authentication Failures - This vulnerability exists when an attacker successfully tricks the system into accepting an invalid or incorrect user as a legitimate identity.
A08:2025 Software or Data Integrity Failures - These failures occur when code or infrastructure fails to distinguish between valid, trusted data and invalid, untrusted data. For instance, applications may rely on plugins, libraries, or modules from untrusted sources, repositories, or Content Delivery Networks (CDNs). A CI/CD pipeline lacking software integrity checks can introduce risks of unauthorized access, malicious code, or system compromise. Another example is a CI/CD process that retrieves code or artifacts from unverified locations without validating signatures or similar mechanisms before use.
A09:2025 Security Logging & Alerting Failures - In the absence of logging and monitoring, attacks and breaches remain undetectable. Furthermore, without effective alerting, rapid and efficient response to security incidents becomes nearly impossible. Failures in security occur whenever there is insufficient logging, continuous monitoring, detection, or alerting to trigger active responses.
A10:2025 Mishandling of Exceptional Conditions - This happens when software fails to prevent, detect, or respond to unusual and unpredictable events, resulting in crashes, erratic behavior, or potential vulnerabilities. This typically involves one or more of the following failures: the application does not prevent the unusual situation, fails to identify it as it occurs, or responds inadequately or not at all afterward.
The training will cover the practical aspects of:
Broken Access Control - Real-world examples of access control failures - Best practices for implementing secure access controls
Security Misconfiguration
- Illustrative examples of common misconfigurations
- Strategies to prevent misconfiguration, including the use of configuration management and automation tools
Cryptographic Failures
- In-depth analysis of failures like weak encryption algorithms and poor key management
- The role of strong cryptographic mechanisms, secure protocols (SSL/TLS), and modern cryptography in web security
Injection Attacks
- Comprehensive breakdown of SQL, NoSQL, OS, and LDAP injection techniques
- Mitigation strategies using prepared statements, parameterized queries, and input escaping
Insecure Design
- Exploration of design flaws that lead to vulnerabilities, such as inadequate input validation
- Study of secure architecture strategies and core design principles
Authentication Failures
- Common issues in authentication processes
- Secure authentication strategies, including multi-factor authentication and robust session management
Software and Data Integrity Failures
- Focus on challenges like untrusted software updates and data tampering
- Implementation of safe update mechanisms and rigorous data integrity checks
Security Logging and Monitoring Failures
- The critical importance of logging security-relevant data and monitoring for suspicious activity
- Tools and practices for effective logging and real-time monitoring to detect breaches early
Requirements
- Fundamental knowledge of the web development lifecycle.
- Practical experience in developing web applications and applying security principles.
Target Audience
- Web Developers
- Technical 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.