Get in Touch

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 - This category involves the enforcement of policies that prevent users from acting beyond their intended permissions. Failures here often result in unauthorized data disclosure, modification, or destruction, or the execution of business functions outside of user limits.


A02:2025 Security Misconfiguration - This occurs when systems, applications, or cloud services are improperly configured from a security standpoint, thereby creating exploitable vulnerabilities.


A03:2025 Software Supply Chain Failures - These refer to compromises or breakdowns in the processes of building, distributing, or updating software. Such issues frequently stem from vulnerabilities or malicious alterations in third-party code, tools, or dependencies upon which the system relies.


A04:2025 Cryptographic Failures - Ideally, all data in transit should be encrypted at the transport layer (OSI layer 4). Challenges such as CPU performance and key management have been mitigated by hardware instructions for encryption acceleration (e.g., AES support) and simplified certificate management through services like LetsEncrypt.org, alongside integrated offerings from major cloud providers. Beyond transport layer security, it is crucial to identify data requiring encryption at rest and additional application-layer encryption (OSI layer 7). Sensitive information such as passwords, credit card numbers, health records, and personal data demands enhanced protection, particularly when subject to regulations like the EU's General Data Protection Regulation (GDPR) or the PCI Data Security Standard (PCI DSS).


A05:2025 Injection - An injection vulnerability allows attackers to embed malicious code or commands (such as SQL or shell scripts) into input fields, tricking the system into executing them as if they were legitimate instructions. This can have severe consequences.


A06:2025 Insecure Design - Insecure design encompasses various weaknesses characterized by missing or ineffective control mechanisms. It is distinct from other Top Ten categories. It is important to differentiate between design flaws and implementation defects, as they arise from different root causes, occur at different stages of development, and require different remediation strategies. A secure design may still suffer from implementation defects that introduce vulnerabilities, whereas an insecure design cannot be remedied by perfect implementation because the necessary security controls were never established. A contributing factor to insecure design is the lack of business risk profiling, which prevents determining the appropriate level of security architecture required.


A07:2025 Authentication Failures - This vulnerability exists when attackers can deceive the system into accepting an invalid or incorrect user as legitimate.


A08:2025 Software or Data Integrity Failures - These failures involve code and infrastructure that fails to protect against invalid or untrusted code and data being treated as trusted. For instance, applications relying on plugins, libraries, or modules from untrusted sources, repositories, or content delivery networks (CDNs) are at risk. An insecure CI/CD pipeline lacking integrity checks can introduce unauthorized access or malicious code. Similarly, CI/CD processes that retrieve code or artifacts from untrusted locations without verifying their authenticity (e.g., via signature checks) pose significant security threats.


A09:2025 Security Logging & Alerting Failures  - Without robust logging and monitoring, attacks and breaches remain undetected. Furthermore, the absence of effective alerting mechanisms hinders the ability to respond quickly and efficiently to security incidents. Gaps in logging, continuous monitoring, detection, and alerting prevent the initiation of active response measures.


A10:2025 Mishandling of Exceptional Conditions - This occurs when software fails to prevent, detect, or respond to unusual and unpredictable situations, leading to crashes, unexpected behavior, or vulnerabilities. This can involve one or more of the following deficiencies: the application does not prevent the unusual situation, fails to identify it as it occurs, or responds inadequately or not at all after the event.

The course will cover practical aspects of:

Broken Access Control
- Practical illustrations of access control failures
- Best practices for secure access control implementation


Security Misconfiguration
- Real-world cases of misconfiguration
- Strategies to prevent misconfiguration, including the use of configuration management and automation tools


Cryptographic Failures
- In-depth analysis of issues like weak encryption algorithms and poor key management
- The importance of strong cryptographic mechanisms, secure protocols (SSL/TLS), and modern cryptography applications in web security


Injection Attacks
- Detailed examination of SQL, NoSQL, OS, and LDAP injection
- Mitigation techniques such as prepared statements, parameterized queries, and input escaping


Insecure Design
- Exploration of design flaws leading to vulnerabilities, such as inadequate input validation
- Strategies for secure architecture and adherence to secure design principles


Authentication Failures
- Common authentication weaknesses
- Secure authentication strategies, including multi-factor authentication and proper session management


Software and Data Integrity Failures
- Focus on risks like untrusted software updates and data tampering
- Implementation of safe update mechanisms and data integrity verification


Security Logging and Monitoring Failures
- The criticality of logging security-relevant events and monitoring for suspicious activity
- Tools and practices for effective logging and real-time monitoring to detect breaches early

Requirements

  • Familiarity with the web development lifecycle.
  • Background in web application development and security practices.

Target Audience

  • Web Developers
  • Technical Leaders
 14 Hours

Number of participants


Price per participant

Testimonials (7)

Upcoming Courses

Related Categories