PT-2025-45579

CVE-2022-12345

·

Publicado

2025-11-09

·

Atualizado

2026-10-03

Descrição por

Pontuação
N/A
Não disponível

Não há classificações de severidade ou métricas disponíveis. Quando houver, atualizaremos as informações correspondentes na página.

Domain 4.0 — Security Operations (28%)
4.1 Hardening and baselines
Secure baselines: establish, deploy, maintain A baseline is the documented minimum secure configuration every system of a given type must meet before production and keep meeting afterward. Sources are CIS Benchmarks, DISA STIGs, and vendor guides (Microsoft Security Compliance Toolkit), customized for the environment. Establish means write and approve the standard. That includes encryption, firewall rules, access control, disabled services, password policy, and logging. Logging is part of the baseline, not a later step. Deploy means push it. Use a golden image, Group Policy, or configuration management, then verify it landed. Maintain means patch, watch for configuration drift, and update the baseline when vulnerabilities, software, or policy change. This is where real breaches happen. Operational practice that matches exam scenarios: harden the OS and apply the baseline before you put the host on the network or hand it over. That is deployment hygiene, not the definition of “establish.” Mobile and wireless Mobile priority controls are full-device encryption, screen lock, MDM policy, and the ability to remote lock or remote wipe a lost device. On BYOD, also segment corporate data (container/MAM) so a wipe can target work data. Related models: COPE, CYOD, COBO. Wireless points that are correct: WEP is broken. TKIP is weak and deprecated. Do not choose either. WPA2 uses the 4-way handshake. An attacker can capture it and offline-brute a weak PSK. Cipher is AES-CCMP. WPA3-Personal uses SAE (Simultaneous Authentication of Equals, Dragonfly), a Diffie-Hellman-style exchange. No hash of the PSK goes over the air, so offline dictionary attacks fail. It also gives forward secrecy and a unique session key per client even when the passphrase is shared. WPA3 requires protected management frames (802.11w). Open networks use Enhanced Open / OWE so traffic is encrypted without a password. Site survey and heat map before you place APs. Disable WPS. Put guests on a separate SSID with client isolation. Hardening targets and apps Server hardening is least privilege, patching, removing unused roles and accounts, and a locked-down baseline. There is no single “first”; both privilege and patching are expected answers. Router and switch hardening: SSH instead of Telnet, SNMPv3 instead of v1/v2c, strong credentials, unused ports and services off, and ACLs on the management plane. Changing IPs for obscurity is not a control. ICS/SCADA and HMI: the exam concern is unauthorized access (often default credentials), plus network segmentation. Availability usually outranks aggressive patching. Unknown or untrusted software goes in a sandbox. For SQL injection and XSS, the primary fix is server-side input validation (and output encoding for XSS). A WAF is a compensating control; it does not replace validation. Quick traps: “establish” is not “apply updates later,” WPA3 is SAE not the 4-way handshake, and obscurity is never the router answer.
4.2 Assets
Assignment and tracking Inventory is the current list of hardware, software, and data: what you have, where it is, and who owns it. It is continuous, not a one-time count. Missing items are shadow IT. Enumeration is the detailed discovery behind that list. It identifies systems and components (a laptop is also CPU, memory, disks, and peripherals) and keeps the record current as assets change. It is more than a headcount. It is not specifically the access-control list. Access is handled by ownership, classification, and least privilege. Classification labels sensitivity and the handling level that follows (public, internal, confidential, restricted). Ownership names the accountable person. That is what routes patches, incidents, and residual risk, and it reduces unowned insider exposure. The owner accepts risk; the custodian (often IT) maintains the asset. Disposal You have sanitization and destruction the right way around now. Sanitization removes data so it cannot be recovered. The device can still be reused. Methods: overwrite (HDDs; clearing for internal reuse, purge for leaving custody), crypto-erase (destroy the key on an SSD or self-encrypting drive that was encrypted the whole time), and degaussing (magnetic media only: HDD, tape. Useless on SSD, flash, and optical). Destruction is physical: industrial shred, pulverize, incinerate, or disintegrate. The media is no longer usable. Use this for the highest sensitivity. A hammer or drill can destroy a few platters in a lab, but the exam answer is industrial destruction, not a casual smash that can leave readable fragments. Certification is the record. A staff member watching is not proof. You still want a certificate of destruction or a sanitization log (method, date, serial, responsible party). Retention is how long you must keep data for legal or business reasons, then dispose. “Keep it forever” is not a retention schedule. SSD trap: degauss does nothing, and a single overwrite can miss blocks because of wear leveling. Prefer crypto-erase if it was always encrypted, otherwise physical destruction.
4.3 Vulnerability management
Identification and scoring CVE names the flaw. The ID is CVE-2022-12345, not the year-number alone. CVSS scores it. A string like CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H is the vector, not the identifier. Base-score bands: 0.1–3.9 Low 4.0–6.9 Medium 7.0–8.9 High 9.0–10.0 Critical Do not map “hard to exploit plus severe impact” to High, or “easier / sensitive systems” to Critical. Attack complexity and impact are inputs to the formula. High complexity lowers the score, so severe impact that is hard to exploit often lands in Medium or High, not automatically High. Critical is only a score of 9.0–10.0. Sensitivity of your systems is an environmental adjustment, not the definition of Critical. False positive: alert, no real issue. False negative: real issue, no alert. False negatives are worse. OSINT is legally available public information. The dark web is hidden (Tor and similar), not automatically illegal. Exam use is threat intel: stolen credentials, exploit sales, chatter. A vulnerability scan identifies. A pen test tries to exploit. Package monitoring watches dependencies and libraries for known vulnerable versions. Responsible disclosure and bug bounties are the other identification paths. Response An exception or exemption delays or skips the fix and must record the accepted risk and the owner. A compensating control is the substitute when the primary control cannot be applied (segmentation, WAF, extra monitoring). Insurance transfers financial impact. It does not remediate the flaw. Exposure factor is the percent of asset value lost in one incident. Single loss expectancy is asset value times exposure factor. Confirm the fix by rescanning. Audit and independent verification are the other validation methods. A third-party test can be that verification, but the objective terms are rescan, audit, and verification.
4.4 Monitoring
Activities and tools Log aggregation collects logs and normalizes formats so they can be compared. It does not correlate or decide an attack. Monitoring is the continuous watching. Alerting is the notice that a rule matched. Alert tuning cuts noise. Reporting is the output. SIEM aggregates, correlates across sources, and alerts. SOAR runs playbooks: enrich, isolate, ticket, notify. “Automate the response” is SOAR, not SIEM. SCAP is the automation framework (OVAL, XCCDF, CVE, and related languages) used to check configurations and vulnerabilities. A benchmark is the standard you compare against, such as a CIS Benchmark or a DISA STIG. SCAP can express a benchmark. It is not the benchmark. NetFlow (and IPFIX) summarizes flows: source, destination, ports, bytes, duration. It does not carry payload, and it does not name the attack. An analyst or a detection rule does that. SNMP polls device status and sends traps. It is a management protocol, not encryption. Prefer SNMPv3. Versions 1 and 2c send community strings in the clear. Data the logs actually contain A packet capture is the full packet as sent. If the session is TLS, you see headers and ciphertext, not the decrypted application data, unless you have the keys. If it is cleartext, the payload is there. Do not treat “pcap shows headers only” as the rule. Full content is the pcap. Summary is NetFlow. File metadata is data about the file: creator or owner, size, created, and modified, sometimes last access. It is not the content, and it is not a list of who opened the file. That comes from access or audit logs. Firewall logs show the connection that was seen: source, destination, ports, action, and time. They do not inventory open ports on the destination. That is a scan. Quarantine isolates a file or host so it can be analyzed. It does not delete it. Archiving is long-term retention. It is not faster search. Hot SIEM storage is what you search. Archive is what you keep for the retention period.
4.5 Enterprise controls
Detection and web controls An IDS detects and alerts. It is usually passive, on a span or tap. An IPS sits inline and can block. Fail-open keeps traffic flowing if the IPS dies. Fail-closed stops it. An NGFW is application-aware and can tie rules to user identity, not just ports. A UTM is the all-in-one box: firewall, IPS, antivirus, and content filtering. A WAF is specifically for web-application attacks such as SQL injection and cross-site scripting. A secure web gateway filters URLs, can apply time-of-day rules, and inspects user web traffic for malware. A centralized proxy gives every branch the same policy and the same reports. An agent-based filter travels with the remote device, so the laptop is still filtered when it is not on the corporate network. NAC You have the agents the right way around. Agent-based NAC installs software and reports richer posture: patches, antivirus, disk encryption, and running processes. Agentless NAC uses network methods such as 802.1X, DHCP fingerprinting, or scanning, and needs no install. It sees less. NAC checks posture before or as the device connects, then allows, denies, or quarantines. 802.1X authenticates the device or user on the port before the port opens. NAC often uses 802.1X, but posture is the extra check. Email, DLP, and placement SPF lists the servers allowed to send for a domain. DKIM signs the message so it can be checked for tampering. DMARC is the policy for SPF or DKIM failure: none, quarantine, or reject, plus reports. S/MIME uses certificates to sign and encrypt the message itself. TLS encrypts the path between mail servers. It does not protect the message after delivery. DLP inspects outbound email and files for sensitive data. Blocking every attachment is too broad. An any-to-any outbound allow is not a secure firewall rule. A screened subnet, also called a DMZ, holds public servers between the outside and the internal network. A GPO linked to an organizational unit applies that department’s rights. SELinux is mandatory access control that restricts Linux processes. A web reputation score is a site’s trustworthiness, used to allow or block before a full content scan.
4.6 IAM
Account lifecycle User provisioning creates the account and assigns rights. Deprovisioning on offboarding is an immediate disable or removal, not a waiting period. Resource provisioning is capacity: virtual machines, storage, and cloud resources. Do not swap those answers. Attestation is the owner periodically confirming that access is still appropriate. Identity proofing confirms the person is real before the credential is issued. Just-in-time permissions and ephemeral credentials exist only for the task, then expire. Temporal accounts are the time-limited account version of the same idea. A passkey is passwordless public-key authentication, usually FIDO2. A biometric or a PIN unlocks the private key on the device. The server never sees a password or the private key. Passwords and factors Map the control to the failure: A password manager addresses too many passwords. A unique-password rule addresses reuse. Complexity and length address guessing and dictionary attacks. Expiration addresses stale passwords. The exam still tests this, even though current guidance prefers length and breach checks. Multifactor authentication limits damage from a stolen or reused password. It does not stop reuse. A software token is an app code. A hard token is a physical code device. A security key is the device you insert or tap. Somewhere you are is location, such as GPS or a network location. Something you are is the biometric. Federation Single sign-on is one authentication for many applications, and it is the usual interoperability answer inside an organization. Federation is the trust that extends that across organizations. LDAP is the directory protocol, not the login. SAML is the enterprise federation assertion. OAuth is authorization, meaning delegated access. OpenID Connect is authentication built on top of OAuth. If the question says “let this app access the account without the password,” choose OAuth. If it says “prove who the user is across companies,” choose SAML or OpenID Connect.
4.7 Automation
Guard rails are automated policy limits on a workflow. They block a bad change before it lands, such as a public storage bucket or a mass delete. They are not physical barriers. Enforcing baselines and standard configurations is how automation stops configuration drift. The same build runs every time. Continuous integration and testing catch defects early and speed delivery. Scripting user provisioning is the onboarding case: create the account, assign groups, and disable it on exit. Resource provisioning is the infrastructure version. A workforce multiplier is the small team plus automation covering work that would otherwise need more people. Employee retention means the repetitive work is gone, so people stay. It is not the control that preserves automation knowledge. That risk sits under ongoing supportability: the scripts need skilled people who can maintain them, regardless of how popular the vendor is. One automation platform is a single point of failure. If it stops, provisioning and response stop, and availability suffers. If it is compromised, the attacker inherits its privileges. The other considerations are complexity, cost, and technical debt from scripts that hide a problem instead of fixing it.
4.8 Incident response
The SY0-701 sequence is preparation, detection, analysis, containment, eradication, recovery, lessons learned. Analysis sits between detection and containment. Detection finds and triages the event. Analysis determines scope, impact, and what you are dealing with. Then contain, then eradicate, then recover. Lessons learned is last, after the incident is closed. Root-cause analysis explains why it happened and what stops a repeat. That is analysis or lessons learned, not detection. Threat hunting is proactive: assume the attacker may already be inside and go look, rather than waiting for an alert. Forensics terms: Acquisition is the unaltered copy, taken in order of volatility. Memory and running state before disk, disk before remote logs and backups. Preservation keeps that copy unchanged. Hashes are how you prove it. Chain of custody records every handler, from collection through court. Legal hold stops deletion so evidence survives. E-discovery is producing that electronic data for a legal case. The report follows the audience. Executives get impact and decisions. Technical staff get indicators and scope. Legal gets custody and handling.
4.9 Investigation sources
Firewall logs show source and destination IP, ports, action, and time. They do not list every open port on the target. OS security logs show successful and failed authentications, account changes, and process or privilege events. Application logs show what that app saw: failed logins with user, time, and IP. They do not contain GPS. Endpoint logs add the process, file, and user on that host. IPS and IDS logs show the signature and the traffic that matched. Network logs and NetFlow show who talked to whom. A packet capture is the full packet when you need payload. Metadata is data about the file or message, not its contents. Correlate on time, IP, user, and process across those sources. One log rarely answers the question. Vulnerability scans, dashboards, and automated reports support the investigation. They are not a substitute for the event logs.
Fornecedores
Produtos afetados
Identificadores relacionados
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾