Enterprise Security Tools & Identity and Access Management

Security+ SY0-701 · Security Operations

By Abu Anns · Last updated 20 November 2026Exam version: SY0-701

Tuning enterprise security capabilities

Objective 4.5 is about modifying the security tools an organization already has to make them more effective. The exam gives you a scenario — a type of attack, a gap in coverage, a new requirement — and asks which capability to adjust. The tools are familiar from earlier guides; what is new here is the operational focus: how each tool is configured, what it can and cannot do, and which one fits the problem.

Firewalls filter traffic by rules; tuning them means adding or removing rules, changing rule order, and switching between allow and deny. IDS/IPS systems detect and (for IPS) block attacks; tuning them means updating signatures, adjusting sensitivity, and choosing between detection and prevention mode. Web filtering blocks access to categories of sites (malware, phishing, gambling) or specific URLs. Operating system security includes host firewalls, security policies, and settings such as disabling autorun. Secure protocols replace clear-text services with encrypted versions. DNS filtering blocks resolution of malicious domains. Email security relies on three standards that work together: SPF (Sender Policy Framework) lists which mail servers are allowed to send for a domain, DKIM (DomainKeys Identified Mail) adds a cryptographic signature to outgoing email so the receiver can verify it was not altered, and DMARC (Domain-based Message Authentication, Reporting, and Conformance) tells receivers what to do with email that fails SPF or DKIM checks — none, quarantine, or reject. NAC (network access control) checks a device's health and identity before allowing it on the network. DLP prevents sensitive data from leaving. EDR (endpoint detection and response) monitors endpoints for suspicious behavior and can isolate a compromised machine automatically; XDR (extended detection and response) extends the same idea across endpoints, networks, cloud, and email.

Identity and access management

Identity and access management (IAM) is the discipline of managing who can access what. It starts with provisioning: creating accounts when someone joins, modifying them when their role changes, and deprovisioning them promptly when they leave — orphaned accounts of departed employees are a classic security failure. Account types include user accounts, privileged accounts (administrators), service accounts (used by applications), and shared accounts (which should be avoided because they destroy accountability).

Access control models define how permissions are assigned. Role-based access control (RBAC) assigns permissions to roles (such as "finance analyst") and users to roles — the most common model in business. Rule-based access control uses rules such as time of day or location. Mandatory access control (MAC) assigns security labels to subjects and objects and enforces access by clearance level, as in military systems; users cannot change permissions themselves. Discretionary access control (DAC) lets the owner of a resource decide who can access it, as in a file-sharing system. Attribute-based access control (ABAC) makes decisions from attributes of the user, the resource, and the environment (department, clearance, time, device). The exam often asks which model fits a scenario: a company that assigns permissions by job function uses RBAC; a military system with classification labels uses MAC; a user sharing a file with a colleague uses DAC.

Authentication: federation, SSO, and MFA

Single sign-on (SSO) lets a user log in once and access multiple applications without logging in again. It is built on federation: one system (the identity provider) authenticates the user and vouches for them to other systems (service providers). The main federation protocols are SAML (Security Assertion Markup Language, used for enterprise web SSO), OAuth (used to grant applications limited access to a user's resources without sharing the password — the "log in with Google" pattern), and OpenID Connect (an identity layer on top of OAuth). LDAP is a protocol for querying directory services (such as Active Directory); LDAPS is the encrypted version. Kerberos is the authentication protocol used in Windows domains, based on tickets issued by a key distribution center.

Multi-factor authentication (MFA) requires two or more factors from different categories: something you know (password, PIN), something you have (a phone, a hardware token, a smart card), and something you are (fingerprint, face, iris). Two factors from the same category (a password and a PIN) are not MFA — that is just two steps of the same factor. MFA methods include authenticator apps (time-based one-time passwords), push notifications, hardware security keys, SMS codes (the weakest method, vulnerable to SIM swapping), and biometrics. Passwordless authentication uses biometrics or hardware keys instead of passwords. Privileged access management (PAM) controls administrator accounts: vaulting privileged credentials, requiring approval for elevated access, and recording privileged sessions. Password concepts the exam tests include complexity, length (longer is better than complex), expiration (modern guidance favors long passwords changed only when compromised), password managers, and account lockout policies.

Privileged access management in depth

Administrator accounts are the highest-value targets in any organization, because compromising one gives an attacker broad control. Privileged access management (PAM) is the set of controls that protects these accounts. Password vaulting stores privileged credentials in an encrypted vault and checks them out only when needed, so administrators never know the actual root or domain admin password. Just-in-time access grants elevated privileges only for a limited time and a specific task, then removes them automatically. Session recording logs everything a privileged user does, providing accountability and evidence for investigations. Approval workflows require a second person to approve a request for elevated access. The exam also tests the principle of separation of duties: no single person should control an entire sensitive process (for example, the person who approves a payment should not be the person who issues it), and least privilege: accounts should have only the permissions their job requires, and administrator access should be used only for administrative tasks, never for everyday work such as browsing email.

Password guidance has changed in recent years, and the exam reflects current thinking: length matters more than complexity, so a long passphrase of ordinary words is stronger than a short password full of symbols. Forced password expiration is now discouraged unless there is evidence of compromise, because frequent changes lead users to choose weak, predictable passwords. Password managers are recommended because they let users have a unique, strong password for every account without memorizing them. Account lockout policies (locking an account after a set number of failed login attempts) deter brute-force attacks but can also be abused to lock out legitimate users, so the threshold should balance security against availability.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A company wants to stop attackers from sending phishing emails that appear to come from the company's domain. It publishes a record listing the only mail servers allowed to send email for its domain. Which standard is this?

Report an error

Q2.An employee logs in to the company portal once in the morning and can then access email, the HR system, and the file server without logging in again. What is this called?

Report an error

Q3.A user logs in with a password and then approves a push notification on her phone. Which authentication factors is she using?

Report an error

Q4.A military organization labels its documents Top Secret, Secret, and Confidential, and users can only access documents at or below their clearance level. Users cannot grant access to others themselves. Which access control model is this?

Report an error

Q5.A company's help desk discovers that a former employee's account is still active six months after the employee left, and it was used to access internal systems last week. Which IAM failure caused this?

Report an error

Q6.A security team wants to detect suspicious behavior on employee laptops — such as a Word document launching PowerShell — and automatically isolate any laptop that shows signs of compromise. Which solution provides this?

Report an error

Q7.A company assigns permissions based on job function: everyone in the 'Accounts Payable' role can approve invoices, and everyone in the 'Auditor' role can view them read-only. When an employee changes jobs, their role changes and their permissions follow automatically. Which access control model is this?

Report an error

Q8.A company wants to ensure that only devices with up-to-date antivirus and the latest patches can connect to the corporate network. Devices that fail the check are placed on a restricted guest network. Which capability provides this?

Report an error