Quibank app: now on the App Store — free, works offline. Get the app ↗

Chapters0/43 ▾
  1. 1.Security Principles & Control Types0/5
    1. The CIA triad: confidentiality, integrity and availability
    2. Identification, authentication, authorization and accounting
    3. Authentication factors and true multifactor
    4. Classifying controls by category and by function
    5. Risk transfer, guidelines and due care in this domain
  2. 2.Risk, Policy Hierarchy & Ethics0/4
    1. Threats, vulnerabilities, likelihood and impact
    2. The risk management lifecycle and the four treatments
    3. Laws, frameworks and the policy document hierarchy
    4. Due care, due diligence and the ISC2 Code of Ethics
  3. 3.Governance, Risk & Compliance0/4
    1. What GRC is for, and who is accountable
    2. Frameworks, standards and where obligations come from
    3. Key metrics, KPIs and key risk indicators
    4. Dashboards, scorecards, reports and AI risk indicators
  4. 4.Continuity, Disaster Recovery & Awareness0/4
    1. Redundancy, business continuity and disaster recovery
    2. Business impact analysis, RPO, RTO and alternate sites
    3. Backup types, offline copies and test restores
    4. Security awareness, culture and AI-powered phishing
  5. 5.Identity Lifecycle Management0/4
    1. Roles definition and provisioning new accounts
    2. Access reviews, movers and privilege creep
    3. Deprovisioning leavers and non-human identities
    4. Identity frameworks and tools: SSO, federation, SCIM, PAM and IGA
  6. 6.Logical Access Controls & Models0/4
    1. Least privilege and need-to-know
    2. Separation of duties, dual control and job rotation
    3. Subjects, objects and discretionary access control
    4. MAC, RBAC, rule-based and attribute-based access control
  7. 7.Network Security Concepts0/5
    1. The OSI and TCP/IP models
    2. IPv4 private addresses, NAT and IPv6
    3. VPNs: what they protect and what they do not
    4. Firewalls, ports and applications
    5. Wireless, Bluetooth, ICS and IoT devices
  8. 8.Network Architecture & Cloud Security0/4
    1. Network segmentation, firewall zones and VLANs
    2. Defense in depth and zero trust
    3. Cloud characteristics and deployment models
    4. Service models and the shared security model
  9. 9.Data Security & Security Operations0/5
    1. Data classification, labeling, data states and masking
    2. Retention and media sanitization
    3. Symmetric and asymmetric encryption, hashing and signatures
    4. Logging, monitoring and event triage
    5. Threat actors, threat intelligence and threat frameworks
  10. 10.Incident Response, Assets & Testing0/4
    1. The incident response plan, team and exercises
    2. The incident response life cycle
    3. Asset lifecycle, configuration and change management
    4. Security testing: teams, scans, application tests and physical tests
Saved in this browser. Move it to another device →
← Incident Response, Assets & Testing

Chapter 10 · Lesson 4 of 4

Security testing: teams, scans, application tests and physical tests

1 min read

In readiness exercises, the red team plays the attacker and the blue team detects and responds. Purple is not a third attacking team; it is the collaboration that feeds red's techniques into blue's detections while the exercise runs.

Before any test, especially phishing simulations or attempts to enter a building, the testers need written authorization that sets scope, targets, timing and rules of engagement. Without it the activity looks like a real attack and the testers have no legal protection.

MethodWhat it does
Vulnerability scanAutomated and broad; reports known weaknesses that may exist, which must be checked for false positives
Penetration testExpert-led; exploits and chains weaknesses to show real impact
Static analysisReads code that is not running; finds source-level defects
Dynamic analysisDrives the running app; finds server misconfiguration, session faults and exposed test paths
Threat modelingDesign-time review of likely threats, such as the STRIDE categories, with a countermeasure for each

Physical tests check people and doors. Tailgating is following someone through a controlled door without their knowledge; piggybacking is when the employee knowingly lets the person in, often after a story about a forgotten badge. Example: a tester walks in behind a delivery driver who never looks back, which is tailgating.

Check yourself

1. During an authorized physical security assessment, a tester slips through a badge-controlled door right behind an employee who never notices him. On a second attempt, a different employee sees him, accepts his story about a forgotten badge, and holds the door open. What are the two techniques, in order?

2. A security team is asked to test whether employees will surrender credentials to a simulated phishing email and whether testers can reach the server room in person. What must happen FIRST?

Facts checked 2026-11-15 · Sources: ISC2 CC Certification Exam Outline, NIST SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management

ISC2 Certified in Cybersecurity (CC) cheat sheet: every key fact on one page →