CISSP Domain 6: Vulnerability Management & Compliance Audits — Mindmap Review Study Guide
═══════════════════════════════════
PART 1: MERMAID MINDMAP
═══════════════════════════════════
mindmap
root((Security Assessment<br/>and Testing))
Purpose and Timing
Purpose
When Involved
Validation and Verification
Validation
Verification
Rigour
Testing a System
Unit Testing
Interface Testing
Integration Testing
System Testing
Methods and Tools
Manual
Automated
Static
Dynamic
Fuzz Testing
Mutation Fuzzers
Generation Fuzzers
Access to Code
White-box
Black-box
Testing Techniques
Positive Testing
Negative Testing
Misuse Testing
Decision Table Analysis
State-based Analysis
Efficiency Techniques
Boundary Value Analysis
Equivalence Partitioning
Operational Testing
Real User Monitoring
Synthetic Performance Monitoring
Regression Testing
Testers and Assessors
Internal
External
Third-Party
SOC Reports
SOC 1
SOC 2
SOC 3
Type 1
Type 2
Audit Roles
Executive Management
Audit Committee
Security Officer
Compliance Manager
Internal Auditors
External Auditors
Metrics
KPIs
KRIs
═══════════════════════════════════
PART 2: TECHNICAL DEFINITIONS & CONCEPTS
═══════════════════════════════════
Purpose and Timing
Purpose of Security Assessment and Testing — To ensure that security requirements and controls are defined, tested, and operating effectively to support the business in achieving its goals and objectives. This provides a sufficient degree of confidentiality, integrity, and availability.
When Security Becomes Involved — Security assessment and testing covers the entire lifecycle in this exact order:
- Gathering and validation of business requirements
- Definition of controls
- Development of new applications and systems
- Ongoing operation
- Eventual retirement and disposal of systems and data
⚠️ EXAM TIP: If asked when security should become involved in testing, look for the earliest possible answer (e.g., “the dawn of time”).
Validation and Verification
Validation — Gathering business requirements to truly understand what the business needs and validating those requirements with relevant stakeholders. You cannot perform testing without first understanding business needs.
Verification — Testing performed once building the product to verify that controls are properly designed and baked into the system.
Rigour — The amount of effort invested in testing, which is driven by the value of the system to the organization. More valuable systems require more testing effort to ensure they effectively support business goals.
Testing a System
Unit Testing — Testing individual units of software as they are developed. For example, testing keyboard input, mouse input, and video output units separately.
Interface Testing — Verifying that communication between two or more units is working correctly through standardized interfaces.
Integration Testing — Testing groups of completed units together to ensure they play nicely with each other.
System Testing — Testing the whole system once all units are completed and integration testing is done.
Methods and Tools
Manual Testing — Hands-on keyboard testing where a person manually reads code or performs actions on a running program.
Automated Testing — Using automated tools (software to test software), such as code scanning tools or vulnerability scanners.
| Method | Description |
|---|---|
| Static | Testing a system that isn’t running; looking at the source code. |
| Dynamic | Testing a running system where the software is actively executing. |
Fuzz Testing — A form of dynamic testing that throws massive amounts of random, chaotic data at a system to identify unexpected errors and vulnerabilities.
| Fuzzer Type | Also Known As | Description |
|---|---|---|
| Mutation Fuzzers | Dumb fuzzers | Have no understanding of input data structure; randomly mutate input data. |
| Generation Fuzzers | Intelligent fuzzers | Have basic understanding of expected input type/structure; generate new chaotic input. |
Access to Code
| Access | Description |
|---|---|
| White-box | Testing where the tester has access to the underlying source code. |
| Black-box | Testing where the tester cannot see the underlying source code; testing the running application. |
Testing Techniques
| Technique | Description |
|---|---|
| Positive Testing | Verifying that a system works as expected (e.g., correct login). |
| Negative Testing | Looking at normal/expected errors to verify they are handled gracefully (e.g., incorrect password). |
| Misuse Testing | Abusing the system as an attacker might (e.g., buffer overflows, SQL injection). |
Decision Table Analysis — A technique used to test system behavior for different input combinations by creating a table of all combinations and expected behaviors. Particularly useful for complex software and requirements management.
State-based Analysis — A technique useful for testing software that exists in different abstract states, such as GUIs and communications protocols like TCP.
Efficiency Techniques
| Technique | Description | Example (Password 8-16 chars) |
|---|---|---|
| Boundary Value Analysis | Focuses testing at the boundaries (extreme ends of input values) where behavior changes. | Tests 7 vs 8, and 16 vs 17. |
| Equivalence Partitioning | Divides inputs into groups (partitions) exhibiting same behavior; tests cover each partition. | Tests within <8, 8-16, and >16 partitions. |
Operational Testing
Real User Monitoring (RUM) — Monitoring the system usage of real users in real-time for usage, performance, and errors.
Synthetic Performance Monitoring — Running scripted transactions via bots or agents to simulate system usage, monitoring functionality, availability, and response times. Good for load or stress testing.
Regression Testing — Testing performed after a change is made to a system to verify that previously tested software continues to perform correctly.
Testers and Assessors
| Tester Type | Description |
|---|---|
| Internal | A company’s own employees testing their own software. |
| External | Hiring an independent external tester, OR sending employees to test a service provider/vendor. |
| Third-Party | Involves three parties: customer, service provider, and independent third-party auditor. |
SOC Reports
| Report | Focus / Description |
|---|---|
| SOC 1 | Focuses on financial reporting risks. |
| SOC 2 | Focuses on the 5 trust principles: Security, Availability, Confidentiality, Processing Integrity, Privacy. |
| SOC 3 | Summarized and sanitized version of SOC 2 for public distribution (marketing tool). |
| Type 1 | Looks at design of a control at a single point in time. |
| Type 2 | Looks at design and operating effectiveness over a period of time (typically a year). |
⚠️ EXAM TIP: As security professionals, we want SOC 2 Type 2 reports.
Audit Roles
| Role | Responsibility |
|---|---|
| Executive Management | Provide tone from the top; promote and fund the audit process. |
| Audit Committee | Board members and senior stakeholders providing oversight of the audit program. |
| Security Officer | Advises on security-related risks to be evaluated in the audit program. |
| Compliance Manager | Manages compliance program to ensure adherence to laws, regulations, standards, and policy. |
| Internal Auditors | Company employees providing assurance that corporate controls are operating effectively. |
| External Auditors | Provide unbiased, independent assurance; independent of the entity being audited. |
Metrics
Metrics Focus — Metrics should always be tied back to business goals and objectives to demonstrate if progress is being made.
| Metric | Direction | Description |
|---|---|---|
| KPIs | Backward-looking | Indicate the achievement of performance targets. |
| KRIs | Forward-looking | Indicate level of exposure to operational risk; monitor future shifts or emerging risks. |