Reports, exports, and data retrieval
Axiad Mesh gives you several ways to get data out of the platform:
- CSV exports from dashboard asset screens and the audit log.
- FAIR reports for quantitative risk analysis.
- The Analytics OData API for BI and analytics tools.
- Bulk retrieval of your Customer Data during and after your agreement.
CSV exports from the dashboard
Asset screens include an Export action that downloads the data as a CSV file.
All data or filtered data
When you export from a non-human identity (NHI) asset screen, Mesh asks you to choose between All data and Filtered data, and the export matches your choice exactly:
- Filtered data contains exactly the records that match your active filters, including any Advanced Filters applied on the asset list. What you filter is what you export.
- All data contains the full dataset for that screen, regardless of any active filters.
This removes any ambiguity about whether an export reflects the on-screen view or the full dataset. If you need a scoped export, build the filter set first, then choose Filtered data.
Large exports
Export queries are optimized for large exports, so they complete promptly even for tenants with large asset or identity inventories.
Export progress and retries
While an export runs, the Export button is disabled and the job's progress is shown. If an export is already running, its status is displayed instead of an error message.
If a temporary service error occurs while an export starts, the export enters a verifying state and checks the actual job status instead of declaring failure. You're never left without a way to retry: once the earlier job has genuinely finished or failed, you can start the export again.
Timestamps in exports
Tenant administrators can choose how timestamps display in the dashboard — in each viewer's browser time zone or in UTC. That preference affects the interface only:
CSV exports and downloaded files always use UTC, regardless of the tenant timestamp display preference. If a downstream pipeline parses timestamps from Mesh exports, treat every exported timestamp as UTC — the display preference never changes exported data.
This keeps exported data canonical for downstream processing, no matter how individual viewers have timestamps displayed.
Export accountability
Every export is recorded in the audit log, from start to finish:
- Both the initiation of an export and its final outcome — success or failure — are logged.
- The entries for one export share the same transaction ID, so you can trace an export from start to finish.
- Each entry is attributed to the user who initiated the export.
- For exports triggered through the API, the client IP address is also recorded.
This gives you full accountability for export operations and lets you troubleshoot failed exports directly from the audit log. For more on working with audit logs, see the Admin Guide.
The audit log itself also exports to CSV: records are written to the file as they're retrieved, so downloads complete reliably even for wide date ranges and datasets of more than 15,000 records. Records aren't duplicated across page boundaries, and running several exports back to back works without errors.
FAIR quantitative risk reporting
Mesh can generate a full FAIR (Factor Analysis of Information Risk) report, enabling quantitative risk analysis based on the industry-standard FAIR methodology. You generate the report for a chosen scope of assets and consume the results directly from the dashboard.
A full FAIR report includes:
- Annualized Loss Expectancy (ALE) quantification with risk-factor breakdowns.
- Impact views at the aggregate level and per asset block.
- Export-ready output for further analysis outside Mesh.
The exact steps to generate a report depend on your tenant configuration. If you don't see FAIR reporting in your dashboard, contact your Axiad representative.
Open FAIR v3.0 terminology
FAIR reporting uses Open FAIR v3.0 standard terminology, so reports stay consistent with the language risk stakeholders expect:
| Label in Mesh | Former label |
|---|---|
| Loss Magnitude (LM) | Single Loss Expectancy (SLE) |
| Loss Event Frequency (LEF) | Annual Rate of Occurrence (ARO) |
Existing reports adopt the current labels automatically, with no breaking changes for existing integrations.
How the model counts losses and identities
- Primary loss forms scale with the number of affected identities.
- Secondary loss forms — competitive advantage, fines and judgments, and reputation — apply once per breach event, not once per identity, as the Open FAIR standard requires.
- Each unique identity is counted once across all risk rules. If several risk rules flag the same people, those people aren't double-counted in the loss calculation.
The methodology behind the figures — the FAIR factor decomposition, the Monte Carlo simulation, and how each risk family maps to loss frequency and magnitude — is explained in Risk quantification. The calibrated constants behind your tenant's figures aren't published; for details about how they're derived for your environment, contact your Axiad representative.
Programmatic access: The Analytics OData API
For BI and analytics tools, Mesh provides a read-only, tenant-isolated OData v4 API. You can query it with standard OData options — for example from Power BI Desktop via Get Data → OData Feed.
The API covers your asset inventory, the software bill of materials and cryptographic inventory behind it, and the risk findings attached to them:
| Entity set | What it covers |
|---|---|
MachineAssets | Machines in your environment |
SoftwareAssets | Software components, with their parent application and canonical package identity |
CryptoElements | Certificates and other cryptographic elements, with their post-quantum security level |
SoftwareDependencies | Which software components depend on which others |
SoftwareCrypto | Cryptographic elements linked to each software component |
MachineSoftwareCorrelations | Which software is installed on which machines |
RiskDetails | Risk findings, per asset |
Agents | Collection agents |
Each entity set also has a ...History twin — for example
SoftwareAssetsHistory — for point-in-time reporting. Historical entity sets
require a snapshot_date filter, and each row is the state as of that date.
See the Analytics OData API reference for the full field list, authentication, and supported query options.
Retrieving your data in bulk
During the term of your agreement, you can extract Customer Data from the Service using the mechanisms described on this page — dashboard CSV exports and the Analytics OData API.
On termination or expiration, upon your written request made before the effective date of termination, Axiad makes a file of your Customer Data available for download, at no cost, for 30 days following the end of the agreement's term. The file is provided in an industry-standard format — for example, JSON or CSV. After the 30-day period, Axiad has no obligation to maintain or provide the data and may delete it unless legally prohibited.
Retention periods for collected identity and audit data during the term are governed by your customer agreement — refer to your agreement or contact your Axiad representative for specifics.
For Axiad's security and compliance documentation, see the Axiad Trust Center.