Hardening Computing Resources & Asset Management

Security+ SY0-701 · Security Operations

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

Hardening: making systems harder to attack

Hardening is the process of reducing a system's attack surface by removing unnecessary features and tightening its configuration. The exam tests hardening across computing resources: endpoints, servers, mobile devices, and wireless networks. The core idea is simple — every open port, every running service, every default account, and every unnecessary application is a potential entry point, and hardening removes or locks down the ones the system does not need.

A secure baseline is a standard, documented configuration for a type of system: which services run, which ports are open, which settings are applied. Every new system is built to the baseline, and deviations are detected and corrected. Common hardening steps include disabling unused services and ports, removing default accounts and changing default passwords, applying the latest patches, enabling a host firewall, disabling unnecessary protocols, and configuring security settings through group policy or configuration management. Endpoint protection adds antivirus/antimalware, host-based intrusion prevention, and endpoint detection and response (EDR) on top of the baseline.

Wireless security

Wireless networks are a favorite exam topic because the protocols have clear security levels. WPA3 is the current standard and the correct answer whenever the exam asks for the most secure Wi-Fi option: it uses Simultaneous Authentication of Equals (SAE) to protect against offline dictionary attacks and provides forward secrecy. WPA2 is still widely used and acceptable, but it is vulnerable to the KRACK attack and to offline dictionary attacks on weak passwords. WPA and WEP are deprecated and insecure — WEP can be cracked in minutes and should never be chosen. For enterprise wireless, WPA2/WPA3-Enterprise uses 802.1X authentication with a RADIUS server, giving each user their own credentials instead of a single shared password. Other wireless considerations: disable SSID broadcast only as a minor obscurity measure (it is not real security), use a strong passphrase, and place access points so their signal does not leak far outside the building.

Mobile devices and application security

Mobile devices need their own controls. Mobile device management (MDM) lets an organization enforce policies on phones and tablets: requiring screen locks, encrypting storage, pushing updates, and remotely wiping a lost device. Bring your own device (BYOD) policies let employees use personal devices for work, which increases risk; the standard mitigations are containerization (separating work data from personal data on the device), MDM enrollment, and remote wipe of the work container only. COPE (corporate-owned, personally enabled) gives the organization more control because it owns the device. Jailbroken or rooted devices should be blocked from corporate resources, because their security controls have been deliberately disabled.

Application security starts with secure coding: input validation, parameterized queries, and output encoding to prevent injection and XSS. Sandboxing runs untrusted code in an isolated environment where it cannot harm the rest of the system — browsers sandbox web pages, and security teams sandbox suspicious files to observe their behavior safely. Application allow listing permits only approved applications to run. Code signing proves software comes from a trusted publisher. And secure baselines apply to applications too: default configurations should be hardened, and unnecessary features disabled.

Asset management: knowing what you own

You cannot protect what you do not know exists. Asset management is the process of tracking hardware, software, and data assets through their lifecycle: procurement, assignment, monitoring, and disposal. Asset inventory is the foundation — a complete, accurate list of every device, application, and data store. Asset tagging (barcodes, RFID, or asset tags) links physical devices to the inventory. Ownership assigns each asset to a responsible person or team. Classification labels assets by sensitivity so the right protections apply.

Disposal is where asset management meets security most directly. Data sanitization removes data from media before reuse or disposal: clearing overwrites data (suitable for reuse within the organization), purging uses stronger methods such as degaussing or cryptographic erase, and destruction physically destroys the media (shredding, crushing, or incineration) for the most sensitive data. A certificate of destruction provides auditable proof that media was destroyed. The exam also tests software asset management: tracking licenses to avoid unlicensed software (a legal and security risk), and ensuring software is supported and patched — end-of-life software with no security updates is a vulnerability.

Endpoint protection and host security

Hardening a system is the foundation; endpoint protection is the active defense that runs on top of it. Traditional antivirus/antimalware software detects known malicious files by comparing them against a database of signatures — effective against known threats, useless against brand-new ones. Host-based intrusion prevention (HIPS) monitors a single system for suspicious activity and can block it. Endpoint detection and response (EDR) goes further: it watches behavior, not just signatures, so it can detect a Word document launching PowerShell or a process injecting code into another process, and it can isolate the endpoint automatically. Host firewalls filter traffic at the individual machine, providing a second layer behind the network firewall. Data execution prevention (DEP) and address space layout randomization (ASLR) are operating-system protections that make memory-based attacks such as buffer overflows harder to exploit. The exam may ask which of these fits a scenario: signature-based antivirus for known malware, EDR for behavioral detection, and a host firewall for per-machine traffic control.

Group policy (in Windows environments) and configuration management tools enforce baselines at scale: they push security settings to every machine, prevent users from changing them, and report machines that drift out of compliance. Patch management is the disciplined process of testing and deploying updates on a schedule — the exam treats unpatched systems as one of the most common and most preventable vulnerabilities. A good patch process includes an inventory of what needs patching, a testing step (so a patch does not break a critical application), a deployment window, and verification that the patch actually installed. Emergency patches for actively exploited vulnerabilities skip the normal schedule: the risk of the vulnerability outweighs the risk of an untested patch.

Finally, hardening applies to embedded and specialized systems too: printers, cameras, and network devices all have default credentials, open services, and firmware that needs updating. A printer with a default admin password is a foothold into the network, and an unpatched camera is a surveillance tool for an attacker. The same hardening discipline — change defaults, disable what is not needed, patch what remains, and monitor for changes — applies to every device on the network, not just servers and workstations.

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 is deploying a new wireless network for its office and wants the strongest available Wi-Fi security. Which protocol should it use?

Report an error

Q2.A security team is hardening a new web server before it goes live. Which action best reduces the server's attack surface?

Report an error

Q3.An employee's company smartphone is stolen from a taxi. The phone contains work emails and customer contact information. Which mobile device management capability best protects the data on the stolen phone?

Report an error

Q4.A company allows employees to use personal phones for work email. The security team wants to ensure that work data can be removed from a phone without deleting the employee's personal photos and messages. Which approach achieves this?

Report an error

Q5.A security analyst receives a suspicious email attachment and wants to observe what it does without risking any production system. What should the analyst do?

Report an error

Q6.A company is decommissioning servers that stored highly sensitive financial data. The hard drives must never be readable again, and the company needs auditable proof of what was done. Which disposal method and documentation should be used?

Report an error

Q7.A security audit discovers several servers running an operating system that the vendor stopped supporting two years ago. No security updates are available for it. What is the primary risk of these servers?

Report an error

Q8.A company wants every new workstation to be built with the same approved settings: a specific set of running services, firewall rules, and security policies. What should the company create?

Report an error