PracticeVideosBlogFlashcards

Security Readiness, Application, and Physical Testing

Key Takeaways

  • Subdomain 5.5 has three parts: security readiness testing, application testing, and physical penetration testing.

  • Readiness testing names blue, purple, and red teaming.

  • Application testing covers vulnerability scanning, static analysis, dynamic analysis, and threat modeling.

  • Physical penetration testing covers phishing, tailgating, and impersonation, and a finding needs a fix and a retest.

  • Source: ISC2 CC Exam Outline v01/2026, subdomain 5.5, and the CC outline page, checked 2026-10-22.

Last updated: October 2026

Security Testing in the 2026 Outline

Subdomain 5.5, Understand security testing, has three parts: security readiness testing (blue, purple, and red teaming), application testing (vulnerability scanning, static analysis, dynamic analysis, and threat modeling), and physical penetration testing (phishing, tailgating, and impersonation). The CC outline page describes entry-level staff supporting these tests rather than leading them.

Source: ISC2 Certified in Cybersecurity Exam Outline, effective September 1, 2026 (v01/2026), subdomain 5.5, and CC outline page, checked 2026-10-22.

Readiness Testing: Blue, Purple, and Red

  • Red teaming simulates an attacker to find weaknesses.
  • Blue teaming defends and detects, and tests how well monitoring and response work.
  • Purple teaming brings the two together so attack and defense findings are shared and improved together.

These are the standard meanings of the three terms the outline names.

Application Testing Methods

  • Vulnerability scanning checks systems and applications for known weaknesses.
  • Static analysis examines code or configuration without running it.
  • Dynamic analysis tests a running application.
  • Threat modeling asks what could go wrong with a design before it is built.
MethodRuns the software?Question it answers
Vulnerability scanningScans the running systemWhich known weaknesses exist here?
Static analysisNoDoes the code or configuration contain risky patterns?
Dynamic analysisYesHow does the running application behave under test inputs?
Threat modelingNo (design review)What could an attacker do to this design?

Physical Penetration Testing

Physical penetration testing checks whether people and facilities resist unauthorized entry. The outline's examples are phishing, tailgating (following an authorized person through a secured door), and impersonation (pretending to belong). A test result is useful only if it leads to a fix, such as a badge procedure, a challenge rule, or awareness training, followed by a retest.

Scenario: The Test Report

A tester follows an employee through a secured door. The finding is not that the door failed; it is that staff do not challenge unknown people. The remediation is awareness training and a challenge procedure, followed by a retest to confirm the change works.

Test Your Knowledge

Which test method runs the application and examines how it behaves?

A

Dynamic analysis

B

Static analysis that reviews the source code without running the application at any point

C

Threat modeling that lists possible attackers, assets, and entry points before any code is written

D

Blue teaming that defends the production environment by monitoring alerts and responding to events

Test Your Knowledge
Matching

Match each testing term to its meaning.

Match each item on the left with the correct item on the right

1

Red teaming

2

Blue teaming

3

Tailgating

Sections you finish are checked off in the contents.