Study guide · Domain 4.0 · 28% of the exam
Security Operations: the SY0-701 objectives in plain English
Security Operations is where the exam stops asking what things are and starts asking what you would do with them on a real network. At 28 percent of the exam, it is the largest domain, and it covers the daily work of the security roles a help desk tech is aiming at: running the tools, handling accounts, answering alerts, and working incidents. It also carries nine objectives, more than any other domain, so it rewards steady, organized study. If you have spent time resetting passwords, imaging machines, and escalating tickets, you have already done pieces of this job by hand.
What the objectives cover
4.1 Given a scenario, apply common security techniques to computing resources.
A secure baseline is the approved starting configuration for a device: you establish it, deploy it to new machines, and maintain it as settings drift. Hardening means removing what a target does not need, and the targets include workstations, servers, switches, routers, cloud infrastructure, mobile devices, IoT devices, embedded systems, and ICS and SCADA equipment. This objective also covers wireless security with WPA3, RADIUS, and EAP methods such as PEAP and EAP-TLS, mobile deployment models like BYOD, COPE, and COBO managed through MDM, and application security basics such as input validation, secure cookies, and sandboxing.
4.2 Explain the security implications of proper hardware, software, and data asset management.
Asset management is the paperwork side of security, and it decides whether you can protect a device at all. It starts with acquisition and procurement, then assignment: every asset gets an owner who is accountable for it, and assets are classified by sensitivity so you know what deserves the strongest protection. You keep an inventory through enumeration, and you monitor and track assets as they move. At end of life, disposal means sanitization or destruction of the media, with certification that it happened. Retention rules and legal holds decide how long data is kept.
4.3 Explain various activities associated with vulnerability management.
Vulnerability management is the ongoing cycle of finding weak points before attackers do. You identify them with vulnerability scanning, penetration testing, audits, responsible disclosure programs, and bug bounties. Then you analyze what you found: confirm the finding is real, separate false positives from false negatives, prioritize by severity using CVSS scores tied to known CVE entries, and manage exceptions where a fix must wait. Response options include patching, segregation, compensating controls, cyber insurance, or accepting the risk. Finally, you validate the fix by rescanning or auditing, and you report the results to asset owners.
4.4 Explain security alerting and monitoring concepts and tools.
Alerting and monitoring is how a security team watches everything at once. You monitor systems, applications, and infrastructure, collect their logs into one place through log aggregation, and set alerts that fire when something looks wrong. The work includes scanning, reporting, and archiving logs for later review, plus validating alerts so real incidents are not buried under noise. Know the tools cold: a SIEM collects and correlates events, SOAR automates responses, EDR watches endpoints, DLP watches data movement, and SNMP traps, NetFlow data, and packet captures fill in what the network is doing.
4.5 Given a scenario, modify enterprise capabilities to enhance security.
Where 4.4 is about watching the tools, 4.5 is about tuning them. Given a scenario, you modify the capabilities an enterprise already runs so they protect better: writing firewall rules and IDS or IPS rules, adjusting web filters and DNS filtering, changing operating system security settings, and configuring file integrity monitoring, DLP, and network access control. It also covers the endpoint stack, meaning endpoint protection platforms plus EDR and XDR. Expect scenario questions where a small, correct change to an existing tool is the answer, not buying something new or rebuilding the network.
4.6 Given a scenario, implement and maintain identity and access management.
This is the identity objective, heavily tested. It covers the account lifecycle: provisioning new accounts, deprovisioning them when someone leaves, assigning permissions, identity proofing at enrollment, and attestation, where managers confirm access is still needed. Know the access control models: mandatory, discretionary, role-based, rule-based, and attribute-based, plus time-of-day restrictions and least privilege. Then the authentication layer: MFA factors and biometrics, hard and soft tokens, password policies, password managers, passwordless sign-in, and privileged access management with just-in-time access, password vaulting, and temporal accounts. It ends with single sign-on and federation: Kerberos, SAML, OAuth, and OpenID Connect.
4.7 Explain the importance of automation and orchestration related to secure operations.
Automation and orchestration means letting scripts and platforms do the repetitive security work: enforcing baselines, setting guard rails, provisioning resources, scaling securely, and reacting faster than a person can. In operations, that looks like automatic ticket creation, escalation, and outage response steps, often tied together through API integrations between tools. The exam also tests the trade-offs honestly. Automation adds complexity and cost, can create a single point of failure, builds technical debt, and needs ongoing support long after the first script works. The safest wins are narrow, well understood tasks.
4.8 Explain appropriate incident response activities.
Incident response is a process with a set order: preparation, detection, analysis, containment, eradication, recovery, and lessons learned. Preparation means training the team and testing the plan with tabletop exercises and simulations before anything goes wrong. During an incident you work the steps in order, then run a root cause analysis so the same hole does not reopen. This objective also covers threat hunting, which is searching for intruders before an alert fires, and digital forensics: legal hold, chain of custody, acquisition of evidence, preservation, reporting, and e-discovery, so evidence holds up later.
4.9 Given a scenario, use data sources to support investigations.
Investigations run on evidence, and 4.9 is about knowing where that evidence lives. The data sources are log data of every kind: firewall logs, application logs, endpoint logs, operating system security logs, IDS and IPS logs, and network logs. Add vulnerability scan results, automated reports and dashboards, and packet captures, which show exactly what crossed the wire. Given a scenario, you pick the source that can actually answer the question: logs tell you who signed in and when, a packet capture shows what was sent, and a scan shows what was exposed at the time.
Worked example
A help desk technician sets up sign-in for a new Microsoft 365 tenant. Users enter a password and then approve a prompt on their phone using a fingerprint scan. Which combination of authentication factors is being used?
The password is something you know, and the fingerprint is a biometric trait, which is something you are. Together they form two distinct factor categories, which is what makes this multifactor authentication.
Why the other options are wrong
- ASomething you know and something you have: The phone is involved, but the approval uses a fingerprint scan rather than simple possession of the device, so the second factor is the biometric, not the phone itself.
- CSomething you are and somewhere you are: No location check is described in the scenario, so somewhere you are is not one of the factors in use.
- DSomething you have and something you do: Something you do refers to behavioral patterns such as typing rhythm, which is not part of this sign-in flow.
Acronyms in this domain
| Acronym | What it means |
|---|---|
| SIEM | Security Information and Event Management |
| SOAR | Security Orchestration, Automation, and Response |
| EDR | Endpoint Detection and Response |
| XDR | Extended Detection and Response |
| DLP | Data Loss Prevention |
| NAC | Network Access Control |
| MDM | Mobile Device Management |
| BYOD | Bring Your Own Device |
| MFA | Multifactor Authentication |
| SSO | Single Sign-On |
| SAML | Security Assertion Markup Language |
| OIDC | OpenID Connect |
| RADIUS | Remote Authentication Dial-In User Service |
| CVSS | Common Vulnerability Scoring System |
| CVE | Common Vulnerabilities and Exposures |
| FIM | File Integrity Monitoring |
Where the help desk meets this domain
Most help desk tickets are this domain done manually, one user at a time. When you walk a new hire through MFA enrollment, verify their identity before a password reset, or remove access on their last day, you are doing 4.6 work: provisioning, identity proofing, and deprovisioning under policy. When you image a laptop from the standard build, you are deploying the 4.1 secure baseline, and when you wipe a returned machine and log it out of inventory, that is 4.2 asset disposal and tracking. The tickets you escalate with good notes become the alerts and log entries that 4.4 monitoring and 4.9 investigations depend on. That is why help desk experience counts for more in this domain than in any other.
The step up into a security role is mostly scope and tooling. Instead of resetting one password, you review the access model that allowed the account. Instead of watching one user, you watch the SIEM queue for the whole company. Your troubleshooting instincts carry over directly: check the logs first, change one thing at a time, and write down what you found. Access reviews, alert triage, and evidence collection are the same habits with a wider view, and they are exactly what junior security roles spend their days on.
Traps to watch for
Keep the federation family straight, because the exam tests the distinctions. OAuth 2.0 is an authorization framework: it grants an application delegated access to resources through tokens, and it does not by itself prove who the user is. OpenID Connect is the authentication layer built on top of OAuth, adding an ID token that does prove identity. Both live in 4.6, alongside SAML, the XML-based federation standard behind most enterprise single sign-on. Kerberos, the ticket based system inside Windows domains, belongs in the same group. If an answer choice credits OAuth alone with authenticating a user, it is wrong.
Two more traps. First, the incident response steps in 4.8 are tested in order: containment comes before eradication, because you stop the spread before you clean up, and lessons learned is always last. Second, data protection as a design topic sits in Domain 3, objective 3.3, not in this domain. Domain 4 mentions data in asset management and in log sources, but if a question is about protecting data by design, think Domain 3. Watch for answer choices that move identity topics into 4.1 as well: baselines and hardening live there, but MFA, SSO, and federation are 4.6.
Now try it. The 5 free sample questions for Domain 4 are in practice mode, with full explanations.
Practice Domain 4 questions