Generating a hash value and making a backup image is the best method to ensure the data on the device is not modified, as it creates a verifiable copy of the original data that can be used for forensic analysis. Encrypting the device, protecting it with a password, or performing a memory scan dump do not prevent the data from being altered or deleted. Verified References: CompTIA CySA+ CS0-002 Certification Study Guide, page
3291

Performing a tabletop drill based on previously identified incident scenarios is the best way to test the changes to the BC and DR plans without any impact to the business, as it is a low-cost and low-risk method of exercising the plans and identifying any gaps or issues. A tabletop drill is a type of BC/DR exercise that involves gathering key personnel from different departments and roles and discussing how they would respond to a hypothetical incident scenario. A tabletop drill does not involve any actual simulation or disruption of the systems or processes, but rather relies on verbal communication and documentation review.
A tabletop drill can help to ensure that everyone is familiar with the BC/DR plans, that the plans reflect the current state of the organization, and that the plans are consistent and coordinated across different functions.
The other options are not as suitable as performing a tabletop drill, as they involve more cost, risk, or impact to the business. Simulating an incident by shutting down power to the primary data center is a type of BC/DR exercise that involves creating an actual disruption or outage of a critical system or process, and observing how the organization responds and recovers. This type of exercise can provide a realistic assessment of the BC
/DR capabilities, but it can also cause significant impact to the business operations, customers, and reputation.
Migrating active workloads from the primary data center to the secondary location is a type of BC/DR exercise that involves switching over from one system or site to another, and verifying that the backup system or site can support the normal operations. This type of exercise can help to validate the functionality and performance of the backup system or site, but it can also incur high costs, complexity, and potential errors or failures. Comparing the current plan to lessons learned from previous incidents is a type of BC/DR activity that involves reviewing past experiences and outcomes, and identifying best practices or improvement opportunities. This activity can help to update and refine the BC/DR plans, but it does not test or validate them in a simulated or actual scenario

Data breach notification laws for personally identifiable information (PII) generally require organizations to provide timely notification to (1) regulatory authorities (regulators/data protection authorities) and (2) affected individuals (customers/data subjects), within legally mandated timeframes.
The Secbay Press CySA+ CS0-003 guide explicitly describes this requirement in multiple places:
* Regulatory reporting + notifying affected individuals:Exact extract (Secbay Press): "Reporting the incident to regulatory authorities and notifying affected individuals in accordance with... privacy laws..."
* Timeliness is required by law:Exact extract (Secbay Press): "Timeliness of Reporting: Adhering to stipulated timeframes for reporting incidents..."
* Customers/affected individuals must be notified within the legally mandated timeframe:Exact extract (Secbay Press): "Sending notifications to customers within the legally mandated timeframe after confirming a data breach." These extracts directly support Option D: Regulators and affected customers.
Why the other options are incorrect
* A (Service providers and business associates): Those relationships may have contractual notification requirements, but breach notification laws for PII focus on regulators and affected individuals.
* B (Law enforcement and the media): These may be involved depending on incident type/requirements, but they are not universally required recipients under PII breach notification laws.
* C (CERTs and industry associations): These are optional coordination entities, not mandated recipients for PII breach notification laws.
References (CompTIA CySA+ CS0-003 documents / study guides used):
* Secbay Press, CompTIA CySA+ Exam Prep Guide (CS0-003): notify regulatory authorities and affected individuals; timeliness requirements; legally mandated timeframe for customer notifications

The correct answer is C. Impact.
The impact metric is the best way to measure the degree to which a system, application, or user base is affected by an uptime availability outage. The impact metric quantifies the consequences of the outage in terms of lost revenue, productivity, reputation, customer satisfaction, or other relevant factors. The impact metric can help prioritize the recovery efforts and justify the resources needed to restore the service1.
The other options are not the best ways to measure the degree to which a system, application, or user base is affected by an uptime availability outage. The timeline metric (A) measures the duration and frequency of the outage, but not its effects. The evidence metric (B) measures the sources and types of data that can be used to investigate and analyze the outage, but not its effects. The scope metric (D) measures the extent and severity of the outage, but not its effects.

Header analysis is the technique of examining the metadata of an email, such as the sender, recipient, date, subject, and routing information. It can help to identify the source of a malicious email by revealing the IP address and domain name of the originator, as well as any spoofing or redirection attempts. References:
CompTIA CySA+ Study Guide: Exam CS0-003, 3rd Edition, Chapter 6, page 240; CompTIA CySA+ CS0-
003 Certification Study Guide, Chapter 6, page 249.