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

CompTIA CySA+ Cheat Sheet: Key Facts

Every key takeaway and common trap from the CompTIA CySA+ study guide on one page, grouped by chapter. Tap a lesson link to read the full explanation.

70 facts · 11 chaptersFacts checked 2026-11-15
  1. Architecture & Log Sources
  2. Indicators of Malicious Activity
  3. Investigation Tools & Threat Hunting
  4. Process Improvement, Automation & AI
  5. Vulnerability Scanning Methods
  6. Analyzing Scan Output
  7. Prioritization, Mitigation & Controls
  8. Attack Frameworks & the Response Process
  9. Incident Response Techniques
  10. Vulnerability Reporting & Communication
  11. Incident Reporting & Metrics

Chapter 1

Architecture & Log Sources

Key takeaways

Common trap

  • Watch for answers that turn an empty result into a clean bill of health. No entries from an edge sensor, a deny-only firewall, an expired retention window or the wrong identity system means the evidence was never collected there, not that the activity did not occur. → Sensor placement, logging levels and retention

Quick reference

What each log source can and cannot prove →
SourceWhat it recordsWhat it cannot tell you
Flow recordsHosts, ports, protocol, bytes, durationUser, process or payload
Firewall without a proxyAllowed or denied connectionsFull URLs requested
DNS resolver logNames queried and answersThe page path or the requesting program
Endpoint agentProcess, parent, command line, logon session, socketsHosts where it is not installed

Chapter 2

Indicators of Malicious Activity

Key takeaways

Common trap

  • Plausible names are the bait. A service called something like a disk or update helper, or a process named svchost.exe, sounds routine on purpose. Choose the answer that checks the path, the parent, the account and the change record, not the one that trusts the name. → Persistence and anti-forensics on hosts
  • Impossible travel is an inference from addresses. If the far-away address is the company's own VPN egress range, the device is the same and the pattern matches the user's baseline, it is a false positive to verify and close, not an account takeover. → Identity and application indicators

Quick reference

Network indicators: DNS abuse, odd protocols and unusual volume →
PatternMost likely meaning
Thousands of long, high-entropy subdomains of one domain, similar-size TXT answers, no connection to the resolved addressDNS tunneling for command and control or data
Hundreds of never-seen names, nearly all NXDOMAIN, then one resolves and a session opens to itDomain generation algorithm malware
Port 443 sessions whose first bytes are an SSH banner and no TLS ClientHelloProtocol tunneled over an allowed port
Tens of gigabytes leaving a host whose role never sends data outData exfiltration

Chapter 3

Investigation Tools & Threat Hunting

Key takeaways

Common trap

  • Bulk-blocking every address in a report feels decisive, which is why it is a favorite distractor. Old or low-confidence indicators on shared infrastructure break legitimate services and expire quickly; the behavior described in the report is what still detects the adversary next month. → Judging and sharing threat intelligence

Quick reference

Packet capture, flow data and network monitoring sensors →
Tool or dataWhat it keepsTypical use
Full packet captureEvery byte, including payloadReassemble a stream in a protocol analyzer to read exactly what was sent
Flow recordsAddresses, ports, times, duration, direction, byte countsProve a conversation happened months later
Network security monitoring sensorOne metadata log per connection, with fields such as the TLS server nameSearchable history of protocol details without storing payload
Signature-based IDSOnly traffic that matched a ruleAlert on known patterns

Chapter 4

Process Improvement, Automation & AI

Key takeaways

Common trap

  • Asking the same model again, or having a second model agree, is not verification. A model can be confidently wrong twice in the same way. Verification means finding the cited events in the real host and network telemetry. → AI in security operations: good uses and main risks

Quick reference

Standard processes: playbooks, runbooks and the case record →
DocumentWhat belongs in itExample item
PlaybookDecision points, who holds authority, escalation and notification orderWho may approve isolating a production server
RunbookExact commands, queries and system steps, with expected outputHow to capture a memory image on an affected host
AI in security operations: good uses and main risks →
RiskWhat it looks likeCorrect response
HallucinationFluent output naming a technique, key or address that is not in the evidenceKeep it out of the case and check every claim in the raw data
Prompt injectionHidden text in a reported email tells the model to call it safeTreat the output as untrusted and judge headers, links and attachments
Data exposureCase notes with customer names sent to an outside serviceFirst confirm retention, reuse for training and who can read it
PoisoningMass-closed true alerts become training labels and the model learns to ignore themReview and sample dispositions before they are used to retrain

Chapter 5

Vulnerability Scanning Methods

Key takeaways

Common trap

  • Wrong answers often claim that a faster scan, a longer timeout or more retries will turn potential findings into confirmed ones or reach a laptop that is not on the network. Speed and timeouts change neither the evidence nor the reachability; only authenticated or agent-based collection does. → Credentialed, non-credentialed and agent-based scanning

Quick reference

Web applications, containers, infrastructure-as-code and baselines →
TargetWhat the scan needsWhat it misses otherwise
Web applicationA maintained session: credentials, a recorded login sequence and the logout link excludedEverything behind the login, such as accounts, payments and administration
ContainerImage scanning in the build pipeline and the registryLibraries inside image layers, which a host scan of the node never reads
Infrastructure-as-codeTemplate scanning before apply plus assessment of the deployed cloud stateDrift, such as a setting changed by hand in the provider console
Hardening baselineA credentialed configuration audit policy run against the adopted benchmarkPer-setting compliance evidence that a vulnerability policy never produces

Chapter 6

Analyzing Scan Output

Key takeaways

Common trap

  • Some output describes an event rather than a weakness. An unlinked file in an upload directory that runs supplied commands and was modified weeks ago is working attacker tooling. Deleting it and closing a ticket destroys evidence; the right path is to preserve the file and host evidence and invoke incident response. → Present, reachable, mitigated or already compromised

Quick reference

Reading the kind of finding: patch, configuration, end of life or shared source →
Kind of findingClue in the outputWhere remediation belongs
Missing patchInstalled version is older than a fixed releaseApply the update, then rescan
MisconfigurationSoftware is current but offers deprecated TLS versions or weak ciphersHardening change in the server's own configuration, then a verification rescan
End of lifeVendor support ended and no patch is listedUpgrade or replace the platform, isolating it in the meantime
Shared sourceHost built from a template, a container image or an infrastructure-as-code definitionFix the source, rebuild, then scan everything built from it

Chapter 7

Prioritization, Mitigation & Controls

Key takeaways

Common trap

  • The most common wrong answer picks the finding with the highest label: a critical flaw on an air-gapped test bench or a powered-off spare server. A medium-rated authentication bypass on an internet-facing customer portal with exploitation in the wild outranks both. → Severity scores versus risk, and how CVSS v4.0 is organized
  • When a register lists a confirmed patch, a removed service, a filtering rule waiting on the patch and a documented decision to do nothing, only the filtering rule is the compensating control. Patching and removal are remediation because the vulnerable code is fixed or gone, and a decision to take no action is risk acceptance, not a control at all. → Classifying controls by type and by function

Quick reference

Classifying controls by type and by function →
ClassificationCategoryExample
TypeAdministrative, also called managerialA written standard requiring quarterly review of server images
TypeTechnicalA configuration baseline enforced by an agent
TypePhysicalA locked rack cabinet with a camera over it
FunctionPreventiveA firewall rule blocking the vulnerable port
FunctionDetectiveAn alert that fires when that port is probed
FunctionCorrective or responsiveA documented rebuild procedure if the host is compromised

Chapter 8

Attack Frameworks & the Response Process

Key takeaways

Common trap

Quick reference

Three attack frameworks, three different questions →
ModelBuilt aroundBest question it answers
MITRE ATT&CKA catalog of tactics and techniquesWhich behaviors do our detections cover or miss?
Cyber Kill ChainSeven ordered stagesWhere would one control have stopped this campaign earliest?
Diamond ModelFour vertices: adversary, capability, infrastructure, victimDo two intrusions share an operator, and what else links to this clue?

Chapter 9

Incident Response Techniques

Key takeaways

Common trap

  • Root cause questions tempt you to pick the first event on the timeline, such as the employee who opened a booby-trapped invoice. Root cause is the condition that made the compromise possible, such as workstations allowed to run macros from internet mail, because fixing that condition is what stops a repeat. → Eradication, recovery and root cause

Chapter 10

Vulnerability Reporting & Communication

Key takeaways

Common trap

  • Wrong answers hand a reader the right artifact for someone else: CVE numbers and host lists to the risk committee, financial framing and risk appetite to the engineers, a raw scan export to the auditor. Ask what this reader must decide or do, then pick the content that serves that one action. → Matching the report to the audience
  • An AI assistant can draft a monthly narrative that claims hosts were remediated or cites a CVE found in no scan result. Adding a machine-generated label or asking a public model for a second opinion is not the fix. The analyst checks every claim against the scan and ticket data of record and stays accountable for what is issued; pasting vulnerability details into an external model also exposes sensitive data. → Credibility: honest severity, controlled disclosure and AI-drafted reports

Quick reference

Matching the report to the audience →
ReaderArtifactWhat it contains
Risk committee or executivesExecutive summaryBusiness exposure, the decision needed about the settlement pause, cost and the risk of deferring
Owning platform teamAction plan or remediation ticketExact hosts, version to install, agreed window, accountable owner and how the fix is verified
Division directorRisk scorecardPosture over several quarters for that business unit
External auditor or assessorCompliance reportControl status and retained evidence that the required assessment was performed

Chapter 11

Incident Reporting & Metrics

Key takeaways

Common trap

  • Any timing metric improves if cases are closed before they are properly validated. When response times keep falling while real intrusions turn up closed as false positives, the fix is to read the metric beside the true-positive rate and a sample review of closures. The same applies to the share of alerts closed by automation: it shows workload absorbed, not whether those closures were right. → Response metrics and how they mislead

Quick reference

After-action reports, root cause and lessons learned →
What the review foundKind of failureCorrective action
No control was ever deployedMissing controlImplement it
The control ran and missed the activityDetection missTune it or change the method
A correct alert sat unread in the queueOutput not acted onFix triage capacity and alert quality
Response metrics and how they mislead →
MetricClock startsClock stops
Mean time to detectThe malicious activity beginsThe team knows about it
Mean time to respondThe team knowsEffective action against the threat
Mean time to remediateThe issue is knownThe underlying cause is eliminated
Mean time to closeThe case opensFormal closure with documentation