Help Desk to Security

Study guide · Domain 5.0 · 20% of the exam

Security Program Management and Oversight: the SY0-701 objectives in plain English

This domain is about who decides, who checks, and who answers when something goes wrong. It carries 20% of the exam, and it covers governance, risk, vendors, compliance, audits, and user awareness. Think of it as the management layer above the technical work in the other domains: it decides what security work happens at all, how it gets funded, and how anyone proves the work was done.

5.0

What the objectives cover

5.1 Summarize elements of effective security governance.

Governance is how an organization directs and controls security. Policies sit at the top: mandatory statements approved by senior management. Standards set the mandatory specifics below them, such as approved products and settings. Procedures give step by step instructions, and guidelines offer optional recommendations. External considerations shape all of it, including regulatory, legal, and industry requirements, plus local, regional, national, and global rules. Governance structures include boards and committees, in centralized or decentralized models. Roles matter. The data owner decides how data is used, the controller decides why it is processed, the processor acts on instructions, the custodian or steward protects it daily, and the data protection officer oversees privacy.

5.2 Explain elements of the risk management process.

Start with risk identification, then assessment: ad hoc, recurring, one-time, or continuous. Qualitative analysis uses labels like high or low, on a risk matrix or heat map. Quantitative analysis uses numbers: exposure factor, single loss expectancy, annualized rate of occurrence, and annualized loss expectancy. Findings go in a risk register with a risk owner. Tolerance, appetite, and threshold define acceptable levels. Inherent risk exists before controls, residual risk after them. Handle risk by accepting, mitigating, transferring, or avoiding it, then track and report it. Business impact analysis identifies critical systems and sets recovery targets: recovery time objective, recovery point objective, mean time between failures, and mean time to repair.

5.3 Explain the processes associated with third-party risk assessment and management.

Third-party risk covers vendors and partners who touch your systems or data. Before signing, you assess them. That can include penetration testing of the vendor, right-to-audit clauses, evidence of internal audits, independent assessments, and supply chain analysis. Selection requires due diligence, checks for conflicts of interest, and questionnaires, with clear rules of engagement for testing. After signing, you keep monitoring the vendor, because their risk becomes your risk. The agreement type sets the terms. A service-level agreement defines performance, a master service agreement sets the terms, and a statement of work defines the tasks. Memorandums of agreement or understanding record shared intent, and a non-disclosure agreement protects confidential information.

5.4 Summarize elements of effective security compliance.

Compliance means following laws, regulations, and rules, and proving it. Reporting can be internal or external, to leadership, regulators, and partners. Non-compliance brings fines, sanctions, other repercussions, loss of a license to operate, and contractual impacts. Monitoring relies on due diligence and due care, plus attestation, a statement of compliance, checked internally and externally. Privacy carries much of it. Laws at local, regional, national, and global levels create legal implications and data subject rights, with duties split between controllers and processors. Purpose limitation means using data only for its collected purpose, and retention rules decide how long you keep it. The GDPR is the example you will see most.

5.5 Explain types and purposes of audits and assessments.

Audits and assessments test whether controls actually work. Attestation is a formal statement that something is true, and an audit is how that claim gets checked. Internal audits include compliance reviews, work overseen by an audit committee, and self-assessments your own teams run. External audits come from regulators, examiners, and independent third parties with no stake in the result. Penetration testing goes further and tries to break in. Tests can be physical, offensive, defensive, or integrated, and the tester may work in a known, partially known, or unknown environment. Reconnaissance comes first, and it can be passive, gathering information without touching the target, or active, interacting with systems directly.

5.6 Given a scenario, implement security awareness practices.

Awareness turns users into part of the defense. Phishing campaigns send simulated phish so staff practice recognizing a phishing attempt, and measure who clicks, who reports, and whether training works. Users learn to submit suspicious messages and respond correctly instead of opening them. Training also covers anomalous behavior, meaning actions that are risky, unexpected, or unintentional, and how to report them. Day to day guidance lives in policy handbooks and covers situational awareness, operational security, password management, data disposal, social engineering, and insider threat. Reporting and monitoring close the loop: you track reports and incidents, follow up with coaching, and measure effectiveness instead of assuming a video worked.

EX

Worked example

Domain 5: Security Program Management and OversightGovernance: policies, standards, procedures, guidelines5-01

Senior leadership at a company approves a document stating that all remote access must use multifactor authentication. A second document lists the specific approved MFA products and the exact settings that must be configured. The second document is BEST described as which of the following?

Correct answer: C. A standard

A standard defines the specific, mandatory requirements that support a policy, such as approved products and exact configuration settings.

Why the other options are wrong

AZ

Acronyms in this domain

AcronymWhat it means
ALEAnnualized Loss Expectancy
SLESingle Loss Expectancy
AROAnnualized Rate of Occurrence
BIABusiness Impact Analysis
RTORecovery Time Objective
RPORecovery Point Objective
MTBFMean Time Between Failures
MTTRMean Time to Repair
SLAService-Level Agreement
MOAMemorandum of Agreement
MOUMemorandum of Understanding
MSAMaster Service Agreement
NDANon-Disclosure Agreement
SOWStatement of Work
GDPRGeneral Data Protection Regulation
DPOData Protection Officer
HD

Where the help desk meets this domain

You already work inside 5.1 every shift, even if nobody labels it that way. The password reset script you follow is a procedure: the exact steps, in order, every time. That procedure exists because a standard requires identity verification before a reset, and the standard exists because a policy, approved by senior management, says accounts must be protected. When you enroll a user in MFA, explain the acceptable use policy, or refuse to bypass a verification step for a caller who sounds rushed, you are carrying out governance, not just being difficult. The same chain explains why you cannot grant a policy exception yourself. Exceptions get documented and approved by the policy owner under 5.1, because the risk has to be accepted by someone with the authority to accept it. You also feel the monitoring and revision part of 5.1 when a script changes after an audit finding and the new version appears in your queue with little more than a version number to announce it.

The rest of the domain shows up in your ticket queue. The phishing simulations users complain about are 5.6: your reports about who clicked and who reported the message are how the program measures whether training works, and the user you coach after a click is doing awareness training in real time. When you open a ticket with an outside vendor, sit on a support call, or check whether a contractor can remote into a system, you are touching 5.3, because the contract, the service-level agreement, and the access rules were settled before that vendor ever reached you. Your ticket notes also become evidence. Retention rules under 5.4 decide how long those records are kept, and auditors working under 5.5 read them to test whether the controls you describe on paper are the controls that actually happen. Auditors sample closed tickets, compare timestamps against the standard, and ask why a step was skipped, which is why a clear note written today can answer a question asked six months from now.

!

Traps to watch for

The biggest trap in this domain is the governance stack in 5.1, and authority is the tell. Ask who approved the document and whether you must follow it. A policy is approved by senior management and is mandatory across the organization. A standard is also mandatory, but it holds the specifics: approved products, required settings, minimum lengths and versions. A procedure is the step by step method you follow to do a task. A guideline is a recommendation only, so words such as optional, recommended, or no penalty point straight to it. Exam questions love to describe one document in the language of another, so match the description to the authority and the level of detail, not to the title the question gives it.

Keep the four risk responses from 5.2 straight, because the exam swaps them constantly. Accept means you live with the risk, usually because fixing it costs more than the loss. Mitigate means you add controls to reduce it. Transfer means someone else carries part of it, and insurance is the classic example, along with contract terms that shift liability to a vendor. If a question describes buying insurance or paying another party to carry the loss, the answer is transfer, even when a control also improves. Avoid means you stop the activity that creates the risk. Watch two more pairs. Attestation, from 5.5, is a statement that something is true, while an audit tests whether the statement holds up, so never pick an audit definition for an attestation question. And in the recovery numbers, the recovery time objective is how long you have to restore a system, while the recovery point objective is how much data, measured in time, you can afford to lose.

Now try it. The 5 free sample questions for Domain 5 are in practice mode, with full explanations.

Practice Domain 5 questions
Domain 4 guideAll guides