A false negative incident in the context of a Security Operations Center (SOC) is when an actual attack or intrusion occurs, but the SOC analyst fails to detect any suspicious events or indicators of compromise. This means that the security measures in place did not work as intended, and the attack went unnoticed.
In David's case, since an attack was initiated and he was not able to find any suspicious events, it is categorized as a false negative incident. This is a critical type of incident because it indicates a failure in the detection capabilities of the SOC, potentially allowing the intruder to cause harm without being detected.
References: The categorization of incidents is a fundamental part of the SOC Analyst's role, as outlined in the EC-Council's Certified SOC Analyst (CSA) training and certification program. The program covers the different types of incidents that can be encountered in a SOC, including true positives, false positives, true negatives, and false negatives, and how to identify and respond to each12345.

URL encoding, also known as percent-encoding, is a mechanism for encoding information in a Uniform Resource Identifier (URI) under certain circumstances. When characters are not allowed in a URI, they are replaced with a percent sign (%) followed by two hexadecimal digits that represent the ASCII code of the character. For example, a space character is not allowed in a URI and is replaced with %20.
References:The answer is verified as per the EC-Council's Certified SOC Analyst (CSA) course materials and study guides, which discuss various encoding schemes used in cybersecurity practices. URL encoding is specifically mentioned as the method for replacing unusual ASCII characters with a percent sign followed by two hexadecimal digits123.

A DHCP Starvation Attack is a type of network attack that aims to deplete the pool of available IP addresses on the DHCP server. The attacker floods the DHCP server with fake DHCP DISCOVER messages using spoofed MAC addresses. If successful, the server will exhaust its address space, denying IP configuration to legitimate clients. This can lead to a denial of service (DoS) for new devices attempting to join the network. Additionally, the attacker may set up a rogue DHCP server to issue malicious IP configurations to clients, potentially redirecting traffic or causing further disruption1.
References: The EC-Council SOC Analyst course and study materials cover various network attacks, including DHCP Starvation Attacks. These resources provide insights into the nature of these attacks, their potential impact, and strategies for prevention and mitigation213.

The Windows event that is logged when a user tries to access a "Registry" key is identified by the event ID
4657. This event ID corresponds to the modification of a registry value. Here's how the process is tracked and logged:
* Detection: The system monitors access to registry keys and values.
* Logging: If a user accesses a registry key, and the key's audit policy is set to log such events, the event is logged.
* Event ID 4657: This specific event ID is used to denote that a registry value was modified, which includes creation, modification, and deletion of registry values.
* Audit Policy: For the event to be logged, "Set Value" auditing must be enabled in the registry key's System Access Control List (SACL).
References: The EC-Council SOC Analyst course materials and study guides detail the various Windows event IDs and their significance in monitoring and analyzing security events. Event ID 4657 is specifically covered as part of the curriculum that deals with registry access monitoring and logging1. Additionally, Microsoft's official documentation provides comprehensive information on this event ID and its role in security auditing2.