What prevention technique does Threat Defense for Active Directory use to expose attackers?
Threat Defense for Active Directory (TDAD) employs Honeypot Traps as a primary prevention technique to detect and expose attackers. These honeypot traps act as decoys within the network, mimicking legitimate Active Directory (AD) objects or data that would attract attackers aiming to gather AD information or exploit AD weaknesses.
Honeypot Trap Functionality:
Honeypot traps are strategically placed to appear as appealing targets, such as privileged accounts or critical directories, without being part of the actual AD infrastructure.
When attackers interact with these traps, TDAD records their actions, which can then trigger alerts, allowing administrators to identify and monitor suspicious activities.
Exposure and Mitigation:
By enticing attackers to interact with fake assets, honeypot traps help expose malicious intentions and techniques. This information can be used for forensic analysis and to enhance future defenses.
This technique allows organizations to expose potential threats proactively, before any real AD resources are compromised.
What is the difference between running Device Control for a Mac versus Windows?
Device Control operates differently on Mac compared to Windows in Symantec Endpoint Protection:
Mac Device Control Functionality:
On macOS, Device Control operates at the volume level, specifically targeting storage devices.
This volume-level control means that SEP enforces policies on storage devices like external drives, USB storage, or other mounted storage volumes rather than peripheral devices in general.
Platform Differences:
On Windows, Device Control can operate at a more granular level (driver level), allowing enforcement across a broader range of devices, including non-storage peripherals.
Why Other Options Are Incorrect:
Option A (driver level) is incorrect for Mac, as SEP does not control non-storage device drivers on macOS.
Option C (kernel level) and D (user level) incorrectly describe the control layer and do not accurately reflect SEP's enforcement scope on Mac.
What is the result of disjointed telemetry collection methods used within an organization?
Disjointed telemetry collection within an organization can result in a lack of granular visibility for investigators. Here's why this is problematic:
Incomplete Data: Disjointed collection methods lead to fragmented data, making it difficult for security teams to get a complete picture of incidents.
Reduced Investigation Efficiency: Without granular and cohesive telemetry, investigators struggle to trace the attack's path accurately, slowing down response times.
Increased Risk of Missing Key Indicators: Critical indicators of compromise may be overlooked, allowing threats to persist or re-emerge in the environment.
Unified telemetry is essential for thorough and efficient investigations, as it provides the detailed insights necessary to understand and mitigate threats fully.
An Incident Responder has determined that an endpoint is compromised by a malicious threat. What SEDR feature would be utilized first to contain the threat?
When an Incident Responder determines that an endpoint is compromised, the first action to contain the threat is to use the Isolation feature in Symantec Endpoint Detection and Response (SEDR). Isolation effectively disconnects the affected endpoint from the network, thereby preventing the malicious threat from communicating with other systems or spreading within the network environment. This feature enables the responder to contain the threat swiftly, allowing further investigation and remediation steps to be conducted without risk of lateral movement by the attacker.
An organization has several Symantec Endpoint Protection Management (SEPM) Servers without access to the internet. The SEPM can only run LiveUpdate within a specified "maintenance window" outside of business hours.
What content distribution method should the organization utilize?
For organizations with Symantec Endpoint Protection Manager (SEPM) servers that do not have internet access and require updates only within a specific maintenance window, the JDB file method is an effective solution:
Offline Content Distribution: JDB files can be downloaded on an internet-connected device and then manually transferred to SEPM, allowing it to update content offline.
Flexible Timing: Since JDB files can be applied during the maintenance window, this method adheres to time restrictions, avoiding disruption during business hours.
Using JDB files ensures that SEPM remains updated in environments with limited connectivity or strict operational schedules.
Devorah
17 days agoPortia
22 days agoGayla
1 months agoCherry
2 months agoYuette
2 months agoShanda
2 months agoEden
3 months agoShizue
3 months agoAdolph
3 months agoGeoffrey
4 months agoNoelia
4 months agoMagnolia
5 months agoLachelle
5 months agoBilly
5 months agoVeronika
5 months agoBo
6 months agoAudry
6 months agoKimberlie
6 months agoRasheeda
6 months agoLawanda
7 months agoRemona
7 months agoShawnta
7 months agoBrett
7 months agoMarya
8 months agoRessie
8 months agoRamonita
8 months agoErasmo
8 months agoTiara
8 months agoGary
8 months agoZona
9 months ago