Skip to content

Get the app

Study guide · Domain 4.0

Security Operations

27% of the exam · 8 exam objectives

Security Operations is the largest domain at 27% of the exam. It covers the daily work of keeping an environment secure: choosing and applying controls, managing assets and vulnerabilities, monitoring and alerting, identity and access management, automation, incident response and the data used in investigations. Most objectives are scenario based, so practise picking the control or step that fits a described situation.

A study feature written by ExamDragon, not part of the real exam. Each heading is one of this domain's 8 exam objectives, as CompTIA states it in the SY0-801 objectives.

4.1Given a scenario, apply mitigating controls, techniques, and solutions to secure the environment.

  • Segmentation, access controls, hardening and sandboxing reduce what an attacker can reach and do; deception technology (honeypot, honeynet, honeyfile, honeytoken, canary account) places decoys that alert when touched.
  • IDS detects and IPS blocks; network based (NIDS/NIPS) watches traffic, host based (HIDS/HIPS) watches one system, and WIPS watches the wireless medium.
  • Firewalls work at Layer 4 (addresses, ports) or Layer 7 (application data); a WAF protects web applications, a UTM combines several functions, rule-based firewalls apply ordered rules and rate limiting slows floods and guessing.
  • Application control uses allow lists (deny by default) or block lists (allow by default); content filters, DLP (agent based or through a centralized proxy) and endpoint tools (antivirus, EDR, XDR) protect users and data.
  • Network access control decides who may connect: 802.1X authenticates at the port, posture checks test device health and captive portals gate guest access; MDM manages mobile devices.
  • Application and repository security: input validation, secure cookies, static code analysis, code signing and secrets scanning.
  • Email security: SPF lists allowed senders, DKIM signs messages, DMARC sets the policy and reporting, BIMI shows a verified logo; operating system security uses Group Policy (Windows) and SELinux (Linux).
  1. The situationA web store suffers SQL injection attempts and customers report spoofed emails from the store's domain.
  2. Step 1Place a WAF in front of the store, because the injection hides in HTTP request data that a Layer 4 rule cannot read.
  3. Step 2Fix the root cause with input validation and static code analysis in the application.
  4. Step 3Check SPF and DKIM, then publish a DMARC record with a quarantine or reject policy and a reporting address.
  5. Where questions turnChoosing a Layer 4 firewall rule for an application attack, or confusing detection (IDS) with prevention (IPS). Also mixing up SPF, DKIM and DMARC: only DMARC tells receivers what to do with failing mail.
  6. The takeawayMatch each control to the layer where the threat lives: application data, code or email domain.
Practise 4.1

4.2Explain the security implications of proper hardware, software, and data asset management.

  • The asset management life cycle runs from planning and scoping, through acquisition and procurement, assignment and accounting, and monitoring and asset tracking, to disposal and decommissioning.
  • Planning and scoping sets which hardware, software and data are needed and the security requirements they must meet.
  • Acquisition and procurement routes purchases, including cloud services, through security review; purchases that bypass it create unmanaged assets.
  • Assignment and accounting records an owner for every asset, which gives accountability when something is lost or misused.
  • Monitoring and asset tracking keeps the inventory accurate over time, including software versions, so missing devices and vulnerable software are found quickly.
  • Disposal and decommissioning removes data before an asset leaves, through sanitization or destruction, with a record as proof.
  1. The situationA new flaw is announced in a popular library and a retired file server is due to go to a recycler the same week.
  2. Step 1Query the software inventory to find every system running the affected library version.
  3. Step 2Hand the results to the vulnerability team for remediation.
  4. Step 3Before the file server leaves, sanitize or destroy its drives and keep the certificate of destruction.
  5. Where questions turnTreating asset management as a one-time inventory. Most failures happen after purchase: no owner recorded, no tracking, or drives sold without sanitization.
  6. The takeawayAn accurate inventory speeds up response; proper disposal keeps data from leaving with old hardware.
Practise 4.2

4.3Given a scenario, perform tasks associated with vulnerability management.

  • Identification methods: vulnerability scanning, IPAM to know every address range to scan, CSPM for cloud misconfigurations and source code review for code flaws.
  • Prioritization uses a severity assessment that weighs the score together with exposure and the value of the system, plus review of penetration test reports.
  • Remediation fixes the weakness, for example by patching or reconfiguring.
  • Verification confirms the fix worked, usually by rescanning or retesting, before an item is closed.
  • Reporting can be internal (status and trends for leadership) or external: bug bounty programs pay outside researchers, and responsible disclosure policies set how outsiders report flaws.
  1. The situationA scan finds the same critical flaw on an internet-facing server and on an isolated lab machine.
  2. Step 1Prioritize the internet-facing server because its exposure makes exploitation more likely.
  3. Step 2Patch it, then rescan to verify the finding is gone.
  4. Step 3Record both findings and their status in the internal report.
  5. Where questions turnClosing a ticket as soon as a patch is installed, without verification. Also confusing a responsible disclosure policy (a reporting process) with a bug bounty (a reporting process with rewards).
  6. The takeawayEqual scores do not mean equal risk; context decides the order, and verification decides when it is fixed.
Practise 4.3

4.4Explain security alerting and monitoring concepts and tools.

  • Monitoring covers systems, applications and infrastructure.
  • Activities: log aggregation, alerting, scanning, archiving for retention, reporting and alert tuning to cut false positives.
  • Tools include benchmarks, agents and agentless collection, SIEM for aggregation and correlation, antivirus, DLP, vulnerability scanners, orchestration and packet analyzers.
  • Protocols: NetFlow summarizes traffic flows, SNMP monitors and manages devices, syslog carries log messages and SCAP standardizes configuration and vulnerability checks.
  • Port mirroring copies traffic to a sensor; dashboards, automated alerts and network management systems present the results.
  1. The situationA new SOC is drowning in alerts and cannot see what happens on its switches.
  2. Step 1Send firewall, server and application logs to a SIEM and tune the noisiest rules.
  3. Step 2Use agentless SNMP monitoring for the switches and port mirroring to feed a network sensor.
  4. Step 3Build a dashboard of open alerts for shift handover and archive old logs for retention.
  5. Where questions turnPicking full packet capture when flow data (NetFlow) is enough, or SNMP when the need is log correlation (SIEM).
  6. The takeawayCollect widely, tune ruthlessly and present clearly.
Practise 4.4

4.5Given a scenario, apply concepts related to identity and access management.

  • Provision accounts with the access needed and deprovision promptly when the need ends; review permissions regularly (access review) to catch permission creep.
  • Identity proofing confirms a person's identity at enrollment; federation and SSO let one sign in work across systems, using SAML (XML assertions), LDAP (directory) and OAuth (delegated authorization).
  • Account types: user, privileged (global or local), service, third-party and emergency access; privileged and emergency accounts need the tightest control and monitoring.
  • MFA factors include hard tokens, soft tokens, biometrics, one-time passwords and backup codes.
  • Access control models: rule-based, role-based, time-based, mandatory (labels and clearances), discretionary (owner decides) and just-in-time (temporary elevation).
  • Password concepts: passkeys, password managers and passwordless methods; best practices on length, complexity, reuse, expiration and age, with compromised credential monitoring, account auditing and policy reports.
  1. The situationDatabase administrators keep permanent admin rights, and a former employee's account still works.
  2. Step 1Disable the former employee's accounts and start an access review of the whole system.
  3. Step 2Move administrators to just-in-time elevation for approved change windows.
  4. Step 3Require MFA for any privileged sign in.
  5. Where questions turnMixing up SAML and OAuth (authentication assertions versus delegated authorization), and mandatory versus discretionary (who decides: the system or the owner).
  6. The takeawayAccess should exist only for the right person, at the right level, for as long as it is needed.
Practise 4.5

4.6Given a scenario, apply automation and orchestration solutions to secure operations.

  • Use cases for automation and scripting: user provisioning, resource provisioning, desired state management, anomaly detection and ticket management.
  • Considerations: guardrails, automation logic, process engineering, complexity, financial cost, process risks and deployment.
  • AI capabilities: agentic (plans and acts), chatbot (converses), predictive analysis (forecasts) and AI-augmented baselines (models normal behavior).
  • Intended outcomes: efficiency and time saving, enforcing baselines, continuous improvements, productivity, reduced downtime and increased proactivity.
  • SecOps builds security into CI/CD pipelines, and workflows connect automation with integrations between tools.
  1. The situationA team wants a script that disables accounts showing suspicious logins.
  2. Step 1Define the automation logic and test it outside production.
  3. Step 2Add guardrails, such as a cap on accounts disabled per hour and human approval beyond it.
  4. Step 3Integrate the workflow with ticket management so every action is recorded.
  5. Where questions turnAssuming more automation is always better. Complexity, cost and process risks are real considerations, and automation without guardrails can cause an outage.
  6. The takeawayAutomation multiplies both good decisions and mistakes, so bound it before you deploy it.
Practise 4.6

4.7Summarize concepts associated with incident response activities.

  • Preparation: training, testing, tabletop exercises (discussion), simulations (realistic practice), playbooks and defined roles.
  • Identification: detection by tools, internal and external advisories and proactive threat hunting.
  • Investigation: digital forensics, chain of custody, e-discovery and preservation of evidence.
  • Containment limits spread, for example by quarantine or isolation; eradication and recovery remove the cause and restore operations.
  • Negotiation (such as with extortionists) and notification or external reporting to stakeholders, customers, law enforcement and mandatory recipients.
  • Post-incident: lessons learned, root cause analysis and post-incident reporting (PIR).
  1. The situationA worm is spreading from one workstation.
  2. Step 1Isolate the workstation to contain the spread.
  3. Step 2Preserve evidence and document the chain of custody, then reimage the host to eradicate and recover.
  4. Step 3Hold a lessons learned meeting and update the playbook.
  5. Where questions turnCalling reimaging containment (it is eradication and recovery), or calling a tabletop exercise a simulation (a tabletop is discussion only).
  6. The takeawayContain first, then eradicate, then learn and feed it back into preparation.
Practise 4.7

4.8Given a scenario, use data, artifacts and sources to support a security investigation.

  • Log and trace data types: access and accounting (logical and physical), device, server, application, authentication, communication, audit, endpoint, network and metadata.
  • Data sources: vulnerability scans, automated reports, NetFlow and IPFIX, surveillance footage, security tools, dashboards and packet captures.
  • File and log integrity is shown with hashes recorded at collection and checked later.
  • System images: a memory dump captures volatile RAM, a bit-level copy duplicates a whole drive including unallocated space and a snapshot captures a system's state.
  • Stakeholders include HR, accounts and legal; log-parsing techniques filter large logs by pattern, field or time.
  1. The situationAn employee is suspected of taking data from a running laptop before resigning.
  2. Step 1Capture a memory dump while the laptop is running, then make a bit-level copy of its drive and record the hashes.
  3. Step 2Parse proxy and endpoint logs for uploads from the laptop.
  4. Step 3Involve HR and legal before any action against the employee.
  5. Where questions turnShutting a system down before capturing memory, or relying on file dates instead of hashes to prove logs were not changed.
  6. The takeawayCollect volatile data first, prove integrity with hashes and bring in the right stakeholders.
Practise 4.8

Key terms

SIEM
Security Information and Event Management
EDR
Endpoint Detection and Response
XDR
Extended Detection and Response
DMARC
Domain-based Message Authentication, Reporting, and Conformance
CSPM
Cloud Security Posture Management
SCAP
Security Content Automation Protocol
SAML
Security Assertions Markup Language
SOAR
Security Orchestration, Automation, and Response
IPFIX
Internet Protocol Flow Information Export
PIR
Post-incident Reporting
After this guide: A laptop infected with ransomware is still connected to the network. Which incident response activity comes next, and what does it involve?
Show the answer

Containment: isolate or quarantine the laptop from the network to stop the spread, then move on to eradication and recovery.

Practise Security Operations

Built to CompTIA's Security+ SY0-801 V8 exam objectives. The explanations, worked examples and traps are ExamDragon's own. Every source this path is built on.