CNSP Certification study materials
CNSP Certification study resources

CNSP Certification study plan

CNSP Certification · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Web Application Security

  • Map the OWASP Top 10 categories to concrete request/response evidence you could capture in a proxy, writing one example per category

  • Configure an intercepting proxy and a browser profile, then capture and annotate five distinct vulnerability classes against a deliberately vulnerable practice app

  • Explain and demonstrate the difference between reflected, stored, and DOM-based cross-site scripting using three separate payload contexts

  • Describe how parameterized queries, output encoding, and Content Security Policy each mitigate a different failure mode, and state one bypass for each mitigation

Your checkpoint

A 10-entry vulnerability notebook: each entry names the weakness class, shows the raw HTTP evidence, states root cause, and gives a concrete fix

Week 2

Web Application Security

  • Walk through the server-side request forgery, insecure deserialization, and broken access control failure modes and identify the trust boundary each one crosses

  • Practice testing for horizontal and vertical privilege escalation by manipulating identifiers, cookies, and hidden fields in a practice app

  • Compare session management designs: cookie flags, token rotation, and logout invalidation, and list the specific test you would run for each

  • Draft a short remediation writeup for one finding that a developer could act on without further questions

Your checkpoint

A one-page access-control and session test checklist with at least 12 checks, each paired with the exact request manipulation used to test it

Week 3

Internal Network Security

  • Enumerate an internal lab subnet with host discovery and service scanning, then record which scan type produced which result and why

  • Identify and safely validate three common internal weaknesses such as SMB signing disabled, LLMNR enabled, or anonymous LDAP bind, without performing exploitation

  • Describe Active Directory authentication flows for Kerberos and NTLM and list the log or artifact each leaves behind

  • Explain segmentation and egress filtering as controls and describe how you would verify them from a compromised host perspective

Your checkpoint

An internal network assessment report for a lab subnet containing an asset inventory, a findings table with severity, and a segmentation verification section

Week 4

Internal Network Security & External Network Security

  • Compare credentialed versus uncredentialed scanning and state when each is appropriate for an internal assessment

  • Map external attack surface discovery steps: certificate transparency, DNS enumeration, and cloud asset identification, and run at least two of them against an authorized target

  • Explain how a perimeter service differs in risk from the same service internally, using at least two concrete examples

  • Summarize how TLS configuration weaknesses and exposed management interfaces are detected and reported

Your checkpoint

An external attack surface inventory for one authorized domain, with discovered hosts, exposed services, and a prioritized remediation list

Week 5

External Network Security & Source-Code Analysis

  • Perform static review of a small code sample and locate at least three injection or authentication flaws by tracing data from source to sink

  • Explain the difference between taint analysis and pattern matching, and state a false positive each approach tends to produce

  • Identify hardcoded secrets, weak cryptography choices, and unsafe deserialization in code and describe the safer alternative for each

  • Correlate a static finding with a dynamic test to confirm exploitability, and document the confirmation step

Your checkpoint

A code review worksheet covering one sample application: finding, source-to-sink path, severity, false-positive assessment, and confirmation method

Week 6

Mobile Application Security & Cloud Security

  • Describe the mobile threat model differences between iOS and Android, including storage, inter-process communication, and code signing, and list the test for each

  • Explain what insecure data storage, improper platform usage, and weak transport security look like on a mobile app and how you would verify them on a test device

  • Map cloud shared responsibility boundaries for IaaS, PaaS, and SaaS and state which controls remain the customer's in each model

  • Identify common cloud misconfigurations such as public storage buckets, over-permissive identity policies, and exposed metadata services, and describe the detection method for each

Your checkpoint

A two-column comparison sheet: mobile vs cloud control failures, with 8 rows pairing the weakness, the verification method, and the owner responsible for the fix

Week 7

Red Team Assessment

  • Explain how a red team engagement differs from a penetration test in scope, rules of engagement, and reporting audience

  • Draft the rules-of-engagement elements that must be agreed before testing: targets, time windows, escalation contacts, and prohibited actions

  • Describe how adversary emulation maps to a threat model and why objective-based testing changes success criteria

  • Outline how findings from a red team exercise are translated into detection engineering improvements

Your checkpoint

A rules-of-engagement and objectives document for a hypothetical engagement, including at least five testable objectives and a deconfliction plan

Week 8

AI/ML Security & Web Application Security & Internal Network Security & External Network Security & Mobile Application Security & Source-Code Analysis & Cloud Security & Red Team Assessment

  • Describe the AI/ML attack surface across the model lifecycle: data poisoning, prompt injection, model extraction, and adversarial input, and name one control per stage

  • Explain why prompt injection is an input-handling problem rather than a model bug, and describe how output handling and tool permissions reduce impact

  • Complete a timed mixed-domain practice set and categorize every missed question by domain to target final review

  • Re-derive the top three weak areas from your error log and write a one-paragraph remediation summary for each

Your checkpoint

A scored practice exam with an error log that maps every miss to a domain and a specific concept to review

Milestones

Week 2: Can explain and demonstrate at least six web application weakness classes with captured evidence, without notes

Week 4: Can describe the full internal and external assessment workflow from scoping to reporting, and has produced two complete lab reports

Week 6: Scores at least 70% on a mixed practice set covering domains 1 through 6, with no domain below 50%

Week 8: Scores at least 80% overall on a full-length timed practice exam, with every domain at or above 65%