This is a very common and difficult-to-diagnose issue after content updates. While the custom rules may be syntactically valid ('Validated'), the underlying schema of events ingested into XSIAM can change with content updates (e.g., a field name changes from event.action' to 'action_name' , or a new normalized field is introduced). If a custom rule relies on a field that no longer exists or has changed its name, it won't find the necessary data to trigger, even if the raw events are present. Using XQL to inspect the actual schema of recent relevant events is the most effective way to identify such discrepancies and then modify the custom rule to match the new schema.

For strict data residency, two fundamental principles apply: 1. The data must physically reside in the specified region. This means that the Cortex XSIAM tenant (the ultimate destination of the logs) must be provisioned in a data center within that region (D). 2. The log data must never leave that region's boundary. Therefore, all Broker VMS collecting sensitive data must also be deployed within that region, and log sources must be configured to send data only to these local Broker VMS (A). The Broker VM acts as a secure conduit, but the data ultimately resides in the XSIAM tenant. Option B (CMEK) is about security, not residency. Option C (redaction) is about data privacy/minimization, not ensuring the entire log stream stays within a region. Option E (local storage with metadata) fundamentally changes the XSIAM ingestion model and is not a standard or supported way to meet residency with full log data.

Broker VM options appear greyed out in the Agent Settings profile when the Local Agent Settings applet is activated without an FQDN. An FQDN is required for agents to resolve and connect to the Broker VM as a download source.

To enforce least privilege for Building 3 administrators, SBAC must be enabled in Restrictive Mode and the administrators' scope must be limited to EG:Building3. This ensures they can only manage endpoints within the Building 3 group, even if those endpoints are also part of other groups, while blocking access to endpoints outside their responsibility.

Both the XSIAM UI and the XSIAM API provide mechanisms to revoke API keys. Option B describes the direct IJI approach, which is straightforward for administrators. Option C describes the typical REST API approach for deleting a resource, where DELETE requests are used to revoke or remove API keys. Option A is a pseudocode function call that might be part of an SDK, but not a direct API endpoint. Option D is an extreme measure that would disrupt all API integrations and is not the targeted way to revoke a single key. Option E is an unsupported and dangerous method of configuration management.