Can custom reports include data from multiple scan policies?

In Spirion's architecture, reporting is decoupled from the individual scan policies that generate the data. This provides several key advantages for organizational reporting:

1. Unified View of the Environment

When you build a custom report, you are querying the central Search Results database. This database aggregates findings from every scan policy you have running, whether it's an endpoint scan, a cloud storage scan (M365/OneDrive), or a database scan.

• Example: You can create a single "PCI Compliance Report" that shows all Credit Card findings across your entire organization, regardless of whether they were found by the "Monthly Workstation Scan" or the "Weekly SQL Server Scan."

2. Filtering by Policy (Optional)

While custom reports include all data by default, you have the power to filter the results if you only want to see specific policies.

• Policy-Specific Reporting: If you need a report specifically for the "Executive Leadership Laptops" policy, you can add a filter in the report wizard to only include results where the Policy Name matches that specific scan.
• Cross-Policy Comparison: You can include the Policy Name as a column in your report to see which scanning strategies are finding the most sensitive data.

3. Aggregation by Business Context

Because custom reports can pull from multiple policies, you can group data by business-relevant fields rather than technical ones.

• By Department: You can group results from five different policies (Email, OneDrive, and Local Drive) into a single view for the "Finance Department."
• By Data Type: You can see every instance of "Social Security Numbers" found across the company, even if those findings came from 50 different scan policies.

4. Proving Program Coverage

One of the most important uses of multi-policy reporting is proving Coverage.

• Benefit: You can create a report that lists all your Targets (endpoints, shares, etc.) and shows which policy is responsible for scanning each one. This ensures there are no "blind spots" in your security program where a target exists but isn't covered by any active policy.

5. Historical Consistency

If you retire an old scan policy and replace it with a new one, a custom report with "Include historical data" enabled will still show the results from the old policy alongside the new one. This ensures your trend lines and risk reduction metrics remain continuous even as your scanning strategy evolves.

Summary

Custom reports are designed to be policy-agnostic.

They act as a "lens" through which you view your entire data risk landscape and enable you to aggregate findings from every corner of your environment into a single, cohesive narrative.