Documentation

Reports and Audit

Overview

The Reports section gives a tenant five views over its own data: a posture score, a compliance control checklist, a unified audit trail, user activity, and a resource inventory. Every report is computed live from your tenant's records when you open it, scoped to your tenant only, and can be exported.

These are single-tenant reports. There is no cross-tenant or portfolio-wide report; an MSSP that manages several client tenants views each tenant's reports in that tenant. See MSSP Console for what a portfolio view does cover.

The home Dashboard is also covered here because its Recent Activity feed is built from the same change history as the audit trail.

Where to Find It

Open Reports in the sidebar (under the Operate group). Reports opens a "Reports & Analytics" page with a card for each report, and a tab bar to switch between them.

ReportRoute
Security Overview/reports/security-overview
Compliance/reports/compliance
Audit Logs/reports/audit-logs
User Activity/reports/user-activity
Resource Usage/reports/resource-usage

Access requires the report:read permission. The same five endpoints (GET /api/reports/audit-logs, user-activity, resource-usage, security-overview, compliance) accept either a portal session or a role-bound API key carrying that permission, so scheduled jobs and AI assistants can read them under the same rule. See REST API Reference.

Common Features

Export

Each report has an Export menu in its header with four formats:

FormatWhat you get
CSVThe report's data rows (after your filters) as a spreadsheet-friendly text file.
ExcelThe same data rows as an .xlsx workbook.
PDFA rendering of the report content on screen, charts included.
ImageThe same rendering as a PNG.

CSV and Excel export what the report currently shows: the Audit Logs export honors the filters and search, User Activity and Resource Usage export the active tab, and Compliance exports the framework summary, or the controls of the selected framework. PDF and Image capture the visible page. A failed export shows an error toast.

Loading, errors, and freshness

  • Report data is cached in the browser for one minute. Reopening a report shortly after does not re-query; reload the page for a fresh read.
  • Each report shows a loading state, an error state with a retry action, and, for Audit Logs and Resource Usage, an empty-state message when there is nothing to show.
  • Filters run in your browser against the data the server returned. The server returns a bounded recent window per report (stated in each section), not your full history.

Deep links

User Activity and Resource Usage keep their tab and filters in the page URL, so a filtered view can be bookmarked or shared (parameters are listed in each section).

How far back the data goes

Audit and activity data is kept for your plan's retention window (free 7 days, Starter 30, Professional 90, Enterprise 365; see Retention by Plan). Older rows are purged by a nightly job, so reports cannot show them.

Security Overview

A snapshot of your tenant's security posture, derived from live configuration data. Open Reports → Security Overview.

Summary cards

CardMeaning
Security ScoreOverall score out of 100: the rounded average of the five component scores below.
Active AlertsCount of unresolved platform alerts for your tenant.
Compliance StatusFrameworks currently fully compliant, shown as compliant/total (for example 1/3).
Critical VulnerabilitiesCount of unresolved configuration-drift records with critical severity. Despite the label, this counts drift, not scanner-detected vulnerabilities.

Score breakdown

A doughnut chart ("Security Score Breakdown") shows five component scores, each 0-100 and each a coverage percentage. A component with nothing to measure scores 100.

ComponentHow it is computed
Identity & accessShare of active users who use two-factor authentication or sign in through single sign-on.
Data protectionShare of stored credential secrets that are encrypted at rest.
Network securityShare of registered deployment targets reachable through a connectivity provider.
Device securityShare of target connections reporting a connected or configured status.
Application securityShare of drift records that are resolved, out of all drift records ever detected.

Other charts

  • Policy Violations by Service: a bar chart of unresolved drift records grouped by app, top 8.
  • Compliance Framework Status: a table of up to 8 frameworks with status (Compliant, Non-Compliant, or Warning for partially compliant or not applicable) and when it was last assessed.
  • Vulnerability Trend: a six-month line chart of drift records detected per month, split Critical, High, Medium, and Low. Critical maps to critical drift, High to warning-severity drift, and everything else to Low; the Medium series has no source and stays at zero.

Time range

The report has no Time Range selector: it always uses the figures above and a fixed six-month trend.

Compliance

A control-by-control view against three built-in frameworks: SOC 2, ISO 27001, and CIS Controls. Open Reports → Compliance ("Compliance Dashboard").

How controls are assessed

Each framework in the catalog has a small set of controls (7 each), and every control is mapped to one automated check of your tenant. The result is evaluated when you open the report; nobody has to attest manually.

CheckPasses when
Access controlAt least one RBAC role is defined.
EncryptionCredential secrets are encrypted at rest.
MFA / SSOActive users use two-factor authentication or SSO.
NetworkDeployment targets are routed through a connectivity provider.
DriftDetected configuration drift has been resolved.
Audit loggingAt least one audit event has been recorded.
ApprovalsAt least one environment approval or rollback policy is configured.

A check is Compliant when everything it covers passes, Non-Compliant when nothing does, Partially Compliant when some does, and Not Applicable when there is nothing to measure (for example, no stored credentials). A control's evidence text states the counts, such as "3/4 active users use MFA or SSO."

Page layout

  • Charts: a radar of framework scores, a status distribution doughnut, and a bar chart of controls by framework.
  • Framework cards: name, description, status badge, score (compliant controls out of assessable controls), counts of total, compliant, and non-compliant controls, and the last assessment date. A framework is Compliant when every assessable control is, Non-Compliant when none is, otherwise Partially Compliant. Select a card to filter the controls table to that framework; select it again to clear.
  • Controls table: Control ID, Title with description, Status, Last Tested, and a View Details link. Last Tested shows the evaluation date, which is today for automated checks. The View Details link is a placeholder and does not open anything yet.

Filters

  • Status dropdown: All Controls, Compliant, or Non-Compliant. Non-Compliant includes partially compliant controls and excludes Not Applicable.
  • Search: matches control ID, title, or description.

Export: with no framework selected the export is the framework summary (name, description, status, score, control counts, last assessment). With a framework selected it is that framework's filtered controls, including requirement, evidence, last tested, and remediation (shown as N/A for automated checks).

This report shows how your configuration maps to the three catalog frameworks. It is a configuration-evidence aid, not a certification or an audit result, and it covers only the listed controls. It does not cover HIPAA, GDPR, PCI, or other frameworks.

Audit Logs

A unified, filterable timeline of what happened in your tenant. Open Reports → Audit Logs.

What is in it

Three record types are merged into one list, newest first:

  • Audit events: sign-ins and sign-outs (with IP address, location when known, and user agent), a failed-login record when the lockout threshold is reached, an SSO sign-in refused because the user quota is full, and app upgrades.
  • Configuration history: every canvas and configuration change: created, updated, deleted, approved, rejected, deployed, reverted, and restored, with the actor, the item, and its details. A rejected entry is shown with Warning status.
  • Deployments: one row per deployment, with action "deploy", the app, the strategy, and a status of Success (succeeded), Failure (failed), or Warning (any other state).

The server returns the 1,000 most recent rows across these sources (drawn from up to 500 audit events, 400 history entries, and 200 deployments). Actions taken during a platform-admin impersonation session carry an impersonator marker in the details. Actions taken by an AI assistant through an API key appear under your tenant's "API Integration" identity. See MCP Server.

Filters

FilterOptions
UserAny user in your tenant, or All Users.
ActionThe distinct actions present in the loaded rows (for example login, logout, created, updated, approved, deployed).
Resource TypeThe distinct resource types present (for example session, app, deployment, and configuration entity types).
StatusSuccess, Warning, or Failure.
From Date / To DateDate pickers; a date is read as the start of that day, so choose the next day to include the whole last day.
SearchFree text across user name, action, resource type, resource name, and IP address.
Reset FiltersClears everything. A "Showing N results" line reports the match count.

Columns

ColumnContent
TimestampDate and time to the second.
UserThe user's name and ID. Events with no user show "System" or the recorded actor name.
ActionAn uppercase badge.
ResourceThe resource type and, when known, its name.
StatusSUCCESS, WARNING, or FAILURE, with a short details line when present.
IP AddressThe client IP and location. Configuration and deployment rows have no IP and show a dash.

The list is virtualized, so long result sets scroll smoothly. The export (CSV, Excel, PDF, Image) uses the filtered rows and adds the full user ID, location, and details fields. The details field can carry change context, so handle exports as sensitive records.

What it does not include

  • Not every action in the portal writes an audit event. Sign-in, sign-out, lockout, JIT quota refusals, and app upgrades are recorded as events; change activity comes from configuration history and deployments.
  • Actions that a delegated MSSP group admin takes on your tenant are recorded in this tenant report as well as in the platform-level audit log. The actor is shown with the label "(delegated group admin)" and the details are marked delegated. See Auditing Delegated Actions.

User Activity

Who is using the platform, and how. Open Reports → User Activity. It has three tabs and a toolbar.

Toolbar

  • User: All Users or one user.
  • Date range: Last 24 Hours, Last 7 Days (default), Last 30 Days, or All Time. It filters the Sessions and Actions tabs; the Overview tab is not date-filtered.
  • Active Only: a checkbox shown on the Sessions tab, limiting it to sessions that are still active.

The tab and filters are kept in the URL as tab (overview, sessions, actions), user, active, and period.

Overview tab

Three charts (User Activity Status: active today versus inactive; User Role Distribution; Most Frequent Actions) above a User Statistics table:

ColumnContent
UserName or email.
RoleThe user's role name.
Last ActiveThe most recent activity time (falls back to last login).
SessionsNumber of sessions in the loaded window.
Avg. DurationAverage length of sessions that have ended, in minutes (zero when none have).
ActionsCount of that user's audit events and configuration changes.
Status"Active Today" or "Inactive", based on activity since local midnight on the server.

Sessions tab

Columns: User, Start Time, End Time / Duration ("Currently Active" for open sessions), IP Address, Location / Device, and Status. A session is active when it has not been revoked and has not expired. A session's duration is only known once it was explicitly ended.

Actions tab

Columns: Timestamp, User, Action, Resource, and Details. It is the user-attributed subset of the audit trail (audit events and configuration changes; deployments are not listed here). Events with no user, such as system events, are omitted.

Limits: the server returns up to 300 sessions and 300 actions, built from the most recent 500 sessions, 500 audit events, and 300 configuration changes. Export uses the active tab with your filters applied.

Resource Usage

An inventory of what your tenant has set up. Open Reports → Resource Usage. It has Overview and Details tabs.

Toolbar

  • Tenant: All Tenants or your tenant. A regular tenant has exactly one entry; this report never lists other customers.
  • Resource Type: shown on the Details tab; All Resource Types or one of compute, storage, network, api, database.
  • Time range: Last 24 Hours, Last 7 Days (default), or Last 30 Days. It applies to the Details tab, filtering by when each resource was created or installed.

URL parameters: tab (overview, details), tenant, resource, period.

What each resource type counts

TypeWhat it representsMetric and unit in Details
computeA registered deployment target (component).deployment_target, 1 instance
storageA developer sandbox's disk usage.sandbox_disk, size in GB
networkA connectivity provider.its provider type, 1 connection
apiAn installed app.enabled_app or installed_app, 1 app
databaseA stored credential.stored_credential, 1 secret

Overview tab

Summary cards (Compute Usage, Storage Usage, Network Usage), two charts (Resource Distribution, Resource Usage Percentage), and a "Resource Usage by Tenant" table with Tenant, Compute, Storage, Network, and Usage % columns plus a Total row. Usage % is the share of your targets whose connection is connected or configured.

Details tab

A row per resource: Timestamp, Tenant, Resource, Type, Metric, and Value.

Read the numbers as counts, not consumption. Compute Usage is the number of deployment targets and Network Usage is the number of connectivity providers, although the card captions say "cores" and "GB". The report shows no cost because it does not meter or bill usage. For plan limits and billing, see Plans and Trial.

Dashboard

The home page (/, titled "Dashboard") is a read-only overview. It is not part of Reports and has no filters or export.

  • Header actions: "Review drift" (opens /pipeline/drift) and "Open pipeline" (opens /pipeline).
  • Pipeline health: summary cards for the pipeline counts, linking into the pipeline and drift pages. See Pipelines and Environments.
  • Apps & Integrations: how many of your installed apps are enabled, with links to the Marketplace and Apps pages.
  • Sandboxes: counts by status when developer sandboxes are enabled for your workspace; otherwise it says they are not enabled yet.
  • Recent Activity: the 6 most recent configuration-history entries (action, item, who, and when) with a link to the pipeline. It is the same change history that feeds the Audit Logs report.

Gotchas

  • Reports cover one tenant. There is no cross-tenant roll-up.
  • On Security Overview, "Critical Vulnerabilities" means unresolved critical drift records.
  • Compliance covers SOC 2, ISO 27001, and CIS Controls only, with a fixed set of automated checks. It is not an attestation.
  • Resource Usage reports counts with no cost metering, so it shows no cost figures.
  • Filters operate on the recent window the server returned, not on your full history, and data older than your plan's retention window is gone.
  • Date filters read a date as the start of the day.
  • Report data is cached for a minute in the browser.
  • Reports are read-only and never change configuration.