To reduce alert noise by prioritizing alerts based on asset sensitivity, which data should you ingest into Google SecOps?

• A. Ingest high-value asset (HVA) data from your CMDB
• B. Ingest dark web forum handlers from your threat intelligence
• C. Ingest IOCs from your threat intelligence system
• D. Ingest TTPs from your threat intelligence system

Answer: (A)

Prioritizing alerts by asset sensitivity hinges on giving your security operations the context of which assets matter most to the business. Ingesting high-value asset data from your CMDB provides a trusted, centralized view of the assets that are most critical—those containing sensitive information, supporting essential services, or carrying high compliance or business impact. With this information, the SecOps platform can score risk and adjust alert priorities so incidents affecting HVAs surface with higher severity and faster workflows, while alerts tied to less critical assets stay lower in the queue. This directly reduces alert noise by ensuring attention is focused on the areas with the greatest potential damage.

Threat intel like dark web forum handlers, IOCs, or TTPs offers valuable external or behavioral context, but they don’t inherently convey internal asset criticality. They help with detection and understanding attacker methods, but they don’t provide the per-asset sensitivity needed to tune alert prioritization.