6.4.1Public-facing web applications are protected against attacks

Defined Approach Requirements:

For public-facing web applications, new threats and vulnerabilities are addressed on an ongoing basis and these applications are protected against known attacks as follows:

Reviewing public-facing web applications via manual or automated application vulnerability security assessment tools or methods as follows:

- At least once every 12 months and after significant changes.

- By an entity that specializes in application security.

- Including, at a minimum, all common software attacks in Requirement 6.2.4.

- All vulnerabilities are ranked in accordance with requirement 6.3.1.

- All vulnerabilities are corrected.

- The application is re-evaluated after the corrections

OR

Installing an automated technical solution(s) that continually detects and prevents web-based attacks as follows:

- Installed in front of public-facing web applications to detect and prevent web?based attacks.

- Actively running and up to date as applicable.

- Generating audit logs.

- Configured to either block web-based attacks or generate an alert that is immediately investigated.

Defined Approach Testing Procedures:

6.4.1 For public-facing web applications, ensure that either one of the required methods is in place as follows:

If manual or automated vulnerability security assessment tools or methods are in use, examine documented processes, interview personnel, and examine records of application security assessments to verify that public-facing web applications are reviewed in accordance with all elements of this requirement specific to the tool/method.

OR

If an automated technical solution(s) is installed that continually detects and prevents web?based attacks, examine the system configuration settings and audit logs, and interview responsible personnel to verify that the automated technical solution(s) is installed in accordance with all elements of this requirement specific to the solution(s).