Skip to Content
1Security
Screens

Reports

Turn Copilot readiness, compliance status and trends into a branded document - PDF, PowerPoint, HTML, CSV or JSON - from the dashboard or over the API.

Reports

The readiness and compliance screens are built for the people who sign in. The Reports screen answers the question that comes after: "How do I hand this to someone who has no 1Security login - under my own brand?"

You find it at Dashboards → Reports, below Copilot readiness. The Print report buttons on the Compliance and Copilot readiness screens open it too, filtered to that report.

What You Can Achieve

Hand over a document, not a login

Download the same data the screens show as a PDF, a PowerPoint deck or a single HTML file. The reader needs no 1Security account.

Put your own brand on it

Company name, logo, brand colour, prepared by and prepared for, footer and confidentiality label. Switch off the 1Security mention for a fully white-label report.

Read it against the right regulations

Choose the regulations the report is read against, or follow what each tenant declared on the Compliance screen.

Automate the delivery

Schedule a template weekly or monthly and have it mailed, or call the API: one request returns the finished file, so a script can produce the monthly report for each client.

Templates

There are seven report types today. Each renders the same data as its screen.

Report typeSource
Copilot readiness assessmentCopilot readiness
Compliance statusCompliance
Trends reviewTrends
Security score reviewSecurity score
Agent inventoryAgents
Action and access reviewAction Center
Incident reportAnomalies - one detection, generated from its drawer

The Copilot readiness assessment goes beyond the pass/fail checks and carries the sections a Copilot readiness review from a consultancy would: oversharing exposure by link type, sensitive data reach and label coverage, content and account hygiene, Copilot licences and agents, the governance controls in place, and a rollout plan derived from the checks. Every figure comes from the same precomputed data the dashboard shows.

Forty-two ready-made templates are always available, filed under five categories. Each is a configuration of one report type - the same sections, layouts and regulations the builder offers - so it can be customised or copied like any other. The tags on a template say which regulation it speaks to, who it is for and how often it is meant to run.

Executive - the exposure test path from consent to a monthly client report:

TemplateReport typeWhat it is for
M365 Access Exposure TestCopilot readiness assessmentThe full test: score, what to fix first, oversharing, sensitive data, hygiene, Copilot and agents, controls, plan, value, licence waste
Exposure test - instant previewCopilot readiness assessmentOne page from directory data minutes after connecting: controls, account hygiene, Copilot licences and agents
Executive one-pagerCopilot readiness assessmentScore, top findings, value delivered and changes since the last report, on one page
Monthly client reportCopilot readiness assessmentThe exposure test as a monthly partner deliverable, changes and value first
Quarterly board briefSecurity score reviewScore, 90-day history, the improvements that pay the most, changes and value for a quarterly board meeting
Partner book roll-upCopilot readiness assessmentOne row per client and the value across the book; queue it as one report per client with the cover sheet
Incident briefingIncident reportTwo pages for management or a client on one detection

The preview and the controls, hygiene and licence parts of the test fill in minutes after connecting; exposure, sensitive data and the value block need the full scan and, for changes, a previous report.

Security:

TemplateReport typeWhat it is for
Sharing exposure reviewCopilot readiness assessmentSharing links by type, open content, external sharing, the widest-reach sites and people, the plan
Identity hygieneCopilot readiness assessmentStale and disabled accounts, guests, ownerless groups, MFA on administrators, conditional access
Third-party apps and consentCompliance statusThe NIS2 and DORA requirements on third-party application reach and consent
External domains and guestsCompliance statusThe NIS2 and GDPR requirements on external domain governance and guest access
Weekly activity scorecardTrends reviewThe last 7 days of the board, biggest movers first; narrow it to the activity trends with Customize
Monthly trends reviewTrends reviewWhat increased and decreased over the last 30 days
Quarterly trends recordTrends reviewEvery trend with its start and current value over the last 90 days
Weekly trends scorecardTrends reviewThe last 7 days on as few pages as possible
Security score briefingSecurity score reviewThe score, the improvements that pay the most and the comparison with similar tenants
Security score recordSecurity score reviewEvery control with its score and the 90-day history

Trend and score reports read what has accumulated: a weekly scorecard needs a week of history, identity hygiene 90 days of sign-ins (from the first day with Entra ID P1), and the sharing review the full scan.

Compliance:

TemplateReport typeWhat it is for
Compliance status briefingCompliance statusReadiness per framework and the open requirements
Compliance audit recordCompliance statusRequirements, attestations and article-level status for every selected framework
NIS2 readinessCompliance statusThe audit record against NIS2 alone
KSC readiness (Polish)Compliance statusThe audit record against the Polish national cybersecurity act alone, in Polish
DORA readinessCompliance statusThe audit record against DORA alone
ISO 27001 evidence recordCompliance statusEvery ISO 27001 control with status, evidence and how it was measured
GDPR data protection statusCompliance statusReadiness and open requirements against GDPR
AI Act and the Polish AI actCompliance statusRequirements and articles of the EU AI Act and the Polish AI act
Compliance weekly changesCompliance statusChanges since the last snapshot first, then readiness by framework, for a weekly run
Incident recordIncident reportThe full file on one detection
NIS2 early warning (24 h)Incident reportArticle 23(4)(a)
NIS2 incident notification (72 h)Incident reportArticle 23(4)(b)
NIS2 final report (1 month)Incident reportArticle 23(4)(d)

Compliance reports are mixed: every requirement states whether it was evaluated, and the header shows the share of checks measured. Incident reports are live from the moment of the detection.

AI governance:

TemplateReport typeWhat it is for
Copilot readiness briefingCopilot readiness assessmentThe verdict and the fixes that matter, for the person deciding on the rollout
Copilot readiness audit recordCopilot readiness assessmentEvery check, ranking and the regulations it speaks to
Copilot readiness scorecardCopilot readiness assessmentVerdict and checks on as few pages as possible
Copilot rollout planCopilot readiness assessmentThe verdict, the plan before and after enabling, Copilot licences and agents, the controls
AI access to restricted dataCopilot readiness assessmentSensitive files, how far an AI assistant reaches them, label coverage, controls, the plan
Agent briefingAgent inventoryHow many agents, where they come from and what to review first
Agent inventory recordAgent inventoryThe full inventory: reach, knowledge sources, capabilities and owners

Agent reports fill from the directory in minutes; the Copilot readiness family needs the full scan for its exposure and sensitive data sections.

Administration and cost:

TemplateReport typeWhat it is for
Weekly action reviewAction and access reviewWhat waits for a decision and which owners owe an answer
Action review recordAction and access reviewOpen actions, owner reviews and security cases with their state
Licence waste and reclaimCopilot readiness assessmentUnassigned and dormant paid seats priced per product, and the stale accounts holding them
Lifecycle hygieneCopilot readiness assessmentInactive sites, ownerless sites and groups, stale accounts, the sites to review
Clean-up progress recordAction and access reviewValue delivered first, then open actions, owner reviews and cases, for a monthly schedule

Action and licence counts are instant; dormancy and stale content wait for 90 days of activity and the full scan.

A ready-made template cannot be edited. Download on the card generates it as it is in the format you pick (PDF, PowerPoint, HTML, CSV or JSON), without opening it; Schedule on the card puts it on a cadence; open it with Customize to adjust it before downloading, or choose Make a copy to keep your own version. A copy is either shared with the whole organization or private to you; the list shows ready-made, shared and private templates side by side, your copies first.

Each template uses one of three layouts:

LayoutLooks likeMade for
BriefingBold cover in the brand colour, large verdictsA decision maker
Audit recordFormal serif typography, dense tablesAn auditor, or the file
ScorecardNo cover, compact, fewest pagesRecurring reviews

What a Readiness Tier Means

A report is only as honest as the data behind it, and the data arrives in stages after a tenant is connected. Every check, requirement, control and report section therefore declares what it needs, and from that declaration it falls into one of four tiers:

TierSays something true…Waits on
InstantMinutes after connectingThe directory read: accounts, licences, apps, devices, group membership, agents
After full scanOnce the first full scan and its precompute have finishedFile, site, link and permission figures; sensitive-data figures also wait for the detections to be rolled up
AccumulatingAfter a number of daysAudit-log or sign-in history (7, 30, 90 or 365 days), a 14-day activity baseline, or a previous report
LiveThe moment something happensAn event, such as the detection an incident report is about

The tier is derived from the declaration, never typed, so a template cannot claim to be instant while carrying a section that reads the full scan. Some checks have two routes: dormant-account checks are instant with Microsoft Entra ID P1 and otherwise wait for 90 days of sign-in history.

For a given tenant, each check is in one of three states:

  • Ready - the data is there; the figure and its verdict are printed, with the time the data is from.
  • Pending - the data is on its way. The report prints the state in place of the figure, with an estimate: Pending · in about 2 days, Pending · after the full scan, Pending · at the next run.
  • Not evaluated - the data cannot arrive as things stand. The reason is printed in place of the figure: Not evaluated · needs Microsoft Entra ID P1, Not evaluated · needs the Conditional Access connection, Not evaluated · needs restricted sensitive-data types declared, or the audit log does not reach back far enough. The dashboard chip names the remedy.

Under the title of every report, and above every tenant's chapter in a multi-tenant document, one line sums it up: Evaluated 23 of 31 checks · data as of 29 Oct 2026 06:10 · 8 pending (in about 2 days) · 0 not evaluated. A partner can read it to a client as "19 of 24 today, 5 more after Thursday's scan".

A check that is pending or not evaluated never counts as a pass. It is left out of every percentage, it does not feed the Access Exposure Score, and it prints its state rather than a value in the PDF, PowerPoint and HTML; the CSV carries a state and a data_as_of column on every row, and the JSON, the REST API and the MCP tools return the same readiness object with the tier, the state, the estimate and the reason, so no integration can mistake "not measured yet" for "met".

Categories and Tags

Templates are filed the way trends are, so a gallery of forty-two does not read like a list. Every template has one category and any number of tags; the gallery has a category rail and a tag filter.

CategoryHolds
ExecutiveThe exposure test path: test, preview, one-pager, monthly client report, board brief, book roll-up
SecuritySharing, identity, apps, domains, activity and score reviews
ComplianceReadiness and audit records per regulation, weekly changes, incident reports
AI governanceCopilot readiness, rollout plan, AI reach into restricted data, agents
Administration and costAction reviews, licence waste, lifecycle hygiene, clean-up progress

Tags come in four kinds. Regulation tags are the frameworks of the Compliance screen - NIS2, KSC, DORA, EU AI Act, ISO 27001, GDPR, the Polish AI act, ISO 42001, SOC 2, NIST CSF 2.0, HIPAA - so a regulation is never a second list. Audience is Board, IT administrator, Auditor or Partner. Cadence is One-off, Weekly, Monthly or Quarterly. Topic is Exposure test, Savings or Governance. On a copy you make, the category and tags are yours to change in the Template group of the builder.

Three more chips sit next to the tags and cannot be edited, because nobody types them: the tier (Instant, After the first full scan, Needs history, Live) is the most demanding tier over the template's sections; Requires … lists the Microsoft licences any of those sections depends on; Needs consent: … lists the connections. They are derived from the sections each time the template is read, so they cannot drift from what the report actually does. Change the sections and the chips follow.

Building a Template

The builder has the settings on the left and a live preview on the right. The preview updates as you type, so you see the document before you save or download anything.

The settings come in five groups.

Template

The template name and a description. Both are for you and your colleagues; they help you find the template in the list.

Design

  • Layout - Briefing, Audit record or Scorecard.
  • Report language - English, Polish, German, French, Spanish, Russian or Ukrainian.
  • Paper size - A4 or Letter.

Branding

  • Company name and Logo. The logo can be PNG, JPEG, WebP or SVG. Large images are scaled down.
  • Brand colour.
  • Prepared by and Prepared for. Prepared for defaults to the tenant name.
  • Contact line, Footer text and Confidentiality label.
  • Mention 1Security - switch it off for a fully white-label report.
  • Link findings to 1Security - switch it off when the readers have no 1Security account.

Content

Set the Report title, then tick the sections to include and use the arrows to put them in order. Every section opens with one line under its title: the report writes it from the data ("12% of files are reachable by anyone with the link; 3 of them hold sensitive content"), or you write your own with Add a description under the ticked section (up to 600 characters). The description travels with the template; it is not one of the fields a per-tenant override can change.

Text sections are your own titled texts, placed anywhere in the order and ticked and moved like any other section: a summary for the board, a tip for the client, a note on what happens next. Add one with Add a text section; it lands after the cover page, and the arrows move it from there. Blank lines split the text into paragraphs. In a document that covers several tenants a text section is printed once, before the chapters. Text sections replace the older Your introduction field, which stays only on templates that still use it.

Copilot readiness assessmentCompliance statusTrends review
Cover pageCover pageCover page
Your introductionYour introductionYour introduction
Verdict and readinessRegulations chosen for this report (always included)Movement in the period
What to fix firstReadiness by frameworkWhat changed most
All checksRequirementsAll trends
Sites to review (top 10)Articles by frameworkHow this was measured
Users with the widest reach (top 10)Changes since the last snapshot
Regulations chosen for this report (always included)How this was measured
How this was measured

A Trends review also has a Period: the last 7, 30 or 90 days. The review covers the trends on the shared Trends board; private trends are left out. For each trend it takes one value per day and compares the first value in the period with the latest one:

  • Movement in the period counts the trends that increased, decreased or stayed unchanged, in total and by category. Categories use the names set on your board.
  • What changed most lists the five largest increases and the five largest decreases, each with its line over the period.
  • All trends lists every trend with its severity, value at the start, value now and change.

A trend with fewer than two values in the period is listed as Not enough history, without a change.

By default the review covers every trend on the board. Under Trends and templates a template can name its own set instead: tick trends from the board and templates from the library, narrow the list by name, category or tag, and add or remove everything shown in one click. That is how a Copilot-only or an administration-only review is made. A template is a trend not yet added to the board: the report counts what matches it when it is generated and lists it without a change, since it has no history. The pick is stored by id and by name, so a connected tenant's own copy of the same trend or template is included when the report covers it.

Regulations

A Copilot readiness assessment and a Compliance status report say which regulations they are read against. Their Regulations chosen for this report section is always included: you can move it, but not leave it out. A Trends review has no such section, because a trend is a count you chose to watch and is not tied to an article.

  • Chosen regulations - you tick the regulations, and every tenant the template renders is read against the same ones. A built-in template opens with the regulations your tenant declared already ticked, or with the one regulation you were looking at when you pressed Report on the Compliance screen, so narrowing a report to one regulation is one click.
  • Each tenant's own regulations - the report follows what each tenant declared on the Compliance screen. A tenant that declared none gets the common baseline. This is the mode for a partner template that covers clients with different obligations.

A report about one regulation is written as such. Leave the title empty and a Compliance status report chosen for NIS2 is titled "NIS2 compliance status" (and its file "nis2-compliance-status-…"), and the Readiness by framework and Articles by framework sections become "NIS2 readiness" and "NIS2 articles". A chapter read against one regulation in the tenant mode gets the same section names; the document title follows the template only, because one document can cover tenants with different declarations.

In a Copilot readiness report the section lists, for each regulation, the articles the checks speak to and their status. In a Compliance report the chosen regulations also decide which frameworks, requirements and articles the other sections show.

Statuses and notes

1Security measures what is connected to it. When the whole picture is different - AI agents that run on people's own machines, devices managed in another tool - a measured status can be right and still not tell the reader everything. In a Compliance report, Statuses and notes lists every requirement with Edit next to it:

  • As measured, note only keeps the measured status and adds your note.
  • Met, At risk (partly met), Not met or Not applicable sets the overall status. A note is required: it says what the measurement does not see.

The report then shows the status you set, marks it Own assessment, and prints the measured status and your note next to it. Articles that rest on an assessed requirement carry an asterisk and a footnote. Nothing measured is hidden or overwritten.

The record is saved for the tenant, not for the template. The same status and note show on the Compliance screen, in every other report, in snapshots and in the API.

For a Copilot readiness report, change a check's targets or snooze it with a note on the Copilot readiness screen. A snoozed check is listed as Snoozed with its note.

A saved template shows its Template ID for the API in the builder.

How this was measured

Every report's footer carries one line: who measured, from what and when ("Measured by 1Security from live tenant data on 3 November 2026") with a link to this section. The How this was measured section is off by default and ticked on the auditor templates; it says in three short paragraphs what the statuses mean, where the figures of that report type come from, and how readiness tiers and the Access Exposure Score are read, with the score's weights in a small table.

  • Met means the check found nothing. At risk means a few matches, still inside the tolerance set for the check. Not met means more than that. No verdict means the check could not be measured yet; it never counts as a pass.
  • Copilot readiness counts come from the latest daily scan of the tenant; compliance requirements are read from live tenant data, manual ones from the owner's attestation; a trends review takes one value per day; the block-based reports (agents, actions, Secure Score) print the dashboard's own counts at the moment of generation.
  • Instant checks work from the directory; others wait for the full scan or for enough history. A check listed as Pending or Not evaluated is left out of every percentage.
  • The Access Exposure Score runs from 0 to 100, higher is better: seven exposure ratios, weighted, with only measured ratios counting. The weights and grades are listed under Access Exposure Score.

Incident Reports

The incident report is the one report type about a single thing rather than the whole tenant: one detection - an anomaly or an incident - from the Anomalies queue. It is generated from the detection's drawer with the Report button, which opens the report in a new tab, where the three tabs of the drawer become sections: Incident at a glance (severity and how it was earned, status, detector, entity, window, score against the alert line), Activity during the incident (the drawer's activity tab - the same entity scope, action group and window, per day and then the event list, capped), Indicators of compromise (distinct addresses with country, network type and provider, devices, client applications, applications and countries drawn from that activity), Response and mitigation (actions taken on the entity since the incident began, actions requested from the drawer), Review history and comments (the History & Comments tab) and Affected entity (the entity, its carriers and the other open detections on it).

What no system can know is written in the dialog and reproduced as entered: a description, the severity and impact, the services affected, the type of threat or root cause, the applied and ongoing mitigation measures, indicators you add, and the Assessment answers a notification form asks for - severe operational disruption or financial loss, considerable damage to others, suspected malicious act, cross-border impact, service recipients informed, reported to law enforcement. Each answer is Yes, No or Not established, and prints as such. The text is saved per detection as you type, so the final report a month later starts from the notification's text.

Executive page, findings and analysis

A document that only reprints the drawer reads as a data dump, so the report opens on an Executive summary page: the significance verdict, severity and status, the stage and its next deadline, the document version (v1 early warning, v2 notification, v3 final - counted from the reports already generated), the TLP marking, the situation in three sentences, the headline findings and who prepared it. Key facts prints the values a notification form asks for - when the incident began, was detected, became known, was contained and resolved, its duration, the number of users affected, the services, the geographic scope, the kinds of damage - typed by the analyst or measured from the detection and marked (measured), so a reader always knows which is which.

Findings is the analyst's spine: numbered claims, each with the evidence it rests on, a confidence (low, medium, high) and a status (confirmed, suspected, ruled out). The editor suggests candidates computed from the activity - new addresses, countries, devices or client applications for this entity, sensitive data touched, activity at a multiple of the usual level, concurrent detections, external actors, deletions and sharing changes, off-hours activity - and you adopt, edit or dismiss them; nothing suggested prints until adopted. Analysis then shows the data behind them: what was new for the entity against its previous 90 days, which sensitive resources were touched and by which actions, how far the activity reached (resources by type, distinct and external actors, shares, downloads, deletions), the incident window against the baseline, and the hour-of-day pattern. Analyst log publishes the review comments you select, Exhibits carries the screenshots you attach (PNG, JPEG or WebP, numbered and captioned), Open questions and next steps says what is unknown and who does what by when, and Sign-off and distribution names who prepared, reviewed and approved the document and what its TLP marking allows.

While you edit, the preview is a draft: a checklist at the top of the editor and at the top of the document lists what the stage and the chosen sections still owe, and every empty field prints a To complete marker in place. The downloaded document prints none of that - an unwritten section is left out rather than printed as "not recorded". Every section also takes a one- or two-sentence note under its title, for the context only your team can give.

NIS2 Article 23 as templates

NIS2 is the first regulatory profile; a profile is a template with a reporting stage, not a different engine. Three ready-made templates follow Directive (EU) 2022/2555, Article 23(4): the early warning due within 24 hours of becoming aware of a significant incident (whether a malicious act is suspected, whether a cross-border impact is possible), the incident notification due within 72 hours (an initial assessment of severity and impact and the indicators of compromise available so far) and the final report due one month after the notification (a detailed description, the type of threat or root cause, applied and ongoing mitigation, cross-border impact where applicable). An intermediate and a progress stage exist for the reports an authority may request.

A staged report carries a Reporting obligation section: the stage, the time the entity became aware of the incident (the detection's first-seen time unless you set it), the three deadlines with whether each was met, and a table of which Article 23(4) point each section of the document answers - and which point the document does not cover, so nothing is implied by omission.

Every generated report is itself recorded on the detection's History & Comments tab (who, when, which template and stage, which format). The deadlines on the timeline read those rows back: an early warning generated before the 24-hour mark shows On time, one after it After the deadline, and a stage with no report yet Not yet generated or Overdue. The notification record is therefore self-documenting; nothing about the deadlines is typed.

The Incident record and Incident briefing templates carry no stage and no obligation section - the same document for an internal file, a client or a management summary. GDPR Article 33 and other regimes are further profiles of the same type and will arrive as more templates.

Over the API, GET /reports/templates/{id}/render?detectionId=… and the MCP tool get_report with detectionId render an incident template for one detection, so a SOC platform can pull the notification document straight from the detection it is working.

Partner Templates for Every Client

A partner builds a template once and uses it for every client tenant:

  • With a saved brand kit, Use partner brand kit (on by default) fills the logo, brand colour and company name from Partner → Branding.
  • Each field has a padlock. A locked field always shows the template's value. An open field may be changed per client tenant under Tenant overrides: for example a different prepared for line, title or set of sections.
  • An override applies when the report covers exactly one tenant. A report over several tenants uses the template's own values.
  • Client name in the report gives a tenant the name the contract uses ("Contoso Ltd" instead of its Microsoft tenant name). It fills the {client} placeholder and the default prepared for line, and is usually set per tenant under Tenant overrides.

Title and file name

Every template carries a title pattern and a file name pattern. The placeholders are {client}, {title} (the report title or the type name), {type}, {partner} (the company name), {date} (YYYY-MM-DD), {month}, {year}, {period} (the window of a trends review) and {regulations} (the short names of the regulations chosen for the template, empty when it follows each tenant's own). An empty placeholder disappears together with its separator, and file names are reduced to ASCII. The defaults, {title} and {title}-{client}-{date}, produce the names reports always had; a partner typically locks {client} – {title} – {month} so a folder of fifty PDFs sorts by client. Both patterns can be locked or left open for tenant overrides like any other field.

One report per client

A partner with a saved template sees One report per client next to the download buttons. Choose the format and the clients (every client tenant the partner reports on is ticked by default) and the dashboard queues one report per tenant - each with that tenant's override, title and file name. The Generated reports tab on the Reports screen shows every pack with its progress, a Download all (ZIP) button once it has finished, and each client's file on its own. Tick Add a cover sheet for the whole pack to get one more file with the cover page and a tenant overview across every chosen client - the partner's own view of the book. A client that fails does not stop the others; its row says why. Files are kept for 24 hours. The same pack is available over the API (see below), so a monthly run can come from your own automation.

Scheduled Reports

Any template can run by itself, and so can any list's Download (see Exports from any list). Schedule sits on every template card, in the builder, and as New schedule on the Schedules tab, where you first pick the template. A ready-made template is scheduled as it is; once you change it in the builder, save it as your copy first so the schedule renders your version. The dialog asks for:

  • Cadence - weekly on a day of the week, or monthly on a day of the month, at an hour and minute in the time zone you pick. The run starts within about fifteen minutes of that time.
  • Scope - This tenant: one report over the tenants the template covers; or, for a partner, One report per client: every client tenant the partner reports on gets its own file with its own override, exactly like the pack described above, with an optional cover sheet for the whole book.
  • Format - PDF, PowerPoint, HTML, CSV or JSON.
  • Recipients - up to twenty email addresses. The mail goes out through the tenant's own alert sender and email theme once the report (or every report of the pack) has finished. By default it carries a link to the report in Generated reports; tick Attach the file to the mail to have small files attached - larger ones are linked. You are the recipient by default, and a schedule needs at least one.

The Schedules tab next to Templates and Generated reports lists every schedule with its cadence, next run, last report and state. Edit changes the cadence, time, format, recipients and attachment of an existing schedule (the template or list it runs stays), the switch pauses and resumes it, and Delete removes it; past reports stay in Generated reports. A schedule pauses itself when its template is deleted, when partner access to the clients ends, when there is no tenant left to report on, or after three failed runs in a row; the row says why, and switching it back on resumes it. Files keep the 24-hour retention; the report history stays.

Every scheduled report opens with Changes since the last report: what moved since the previous run of the same schedule - the figures that moved, the checks that changed state and the articles that changed status. The first run has nothing to compare against and prints Baseline - first report of this schedule; changes appear from the next run. Schedules are also available over the API; see the API reference.

Value Delivered and Licence Waste

Two sections can be added to every report type. Value delivered answers "what did this get us" for the period since the previous report of the schedule - or, for a report with no predecessor, the last 30 days, which the section says:

LineWhere the number comes from
Exposures closedActions from the Action Center that succeeded in the period and were not undone, grouped by what they achieved: sharing removed, access revoked, accounts secured, app consent removed, licences reclaimed, owners assigned, content removed. Actions that close no exposure are listed as other.
Findings resolvedPolicy findings whose episode closed in the period.
Licences reclaimedPaid seats held at the previous report and no longer held now, per product, priced per month at the price below. The first report prints the baseline; the comparison starts with the next one.
Hours savedThe arithmetic printed with the figure: 2 h per report, 15 min per action, 10 min per finding, over the reports delivered, actions completed and findings resolved in the period.
Audit readinessThe compliance readiness percentage per selected regulation, its change since the previous report, and how many checks were evaluated next to it, so a higher number earned by fewer checks is visible as such.

The partner Value delivered screen computes from the same functions, so the screen and the report never disagree on what an exposure closed is.

Licence waste prices the seats nobody uses. For every paid product it lists the purchased, unassigned seats (bought minus assigned), the seats on dormant accounts (disabled, or no activity for 90 days or more) and the monthly waste: (unassigned + dormant) × the price per seat per month, summed in euros. The price is Microsoft's public list price in EUR for an annual commitment, per user per month, excluding VAT. Products with a known list price include the Microsoft 365 Business plans, the EEA (no Teams) Microsoft 365 and Office 365 enterprise suites, the F1 and F3 frontline plans, Exchange Online Plan 1 and 2, Microsoft Entra ID P1 and P2, Microsoft Intune Plan 1, the Microsoft Defender for Office 365 plans, Microsoft 365 E5 Security and E5 Compliance, Microsoft 365 Copilot, and the Visio and Project plans. A product without a list price - including the legacy enterprise suites sold with Teams, whose renewal prices vary by agreement - is listed with its seats but not counted, and the section says how many were left out.

To use what you actually pay, open Licence prices on the Licenses screen and type a price next to the product: a tenant price wins over the list price in every report about that tenant, and a blank price restores the list price. A partner does this per client.

Access Exposure Score

One number states how exposed a tenant is: the Access Exposure Score, 0 to 100, higher is better, like Secure Score, so a partner can print the two side by side. It is built from seven ratios the Copilot readiness assessment already measures, each with a weight (the points at stake) and a cap (the share at which all of them are lost):

ComponentWeightAll points lost at
Files behind "anyone" links2010 % of files
Sensitive files behind "anyone" or external links255 % of files
Guests among accounts1030 %
Enabled accounts idle for 90 days1025 %
Administrators without multi-factor authentication15100 %
Third-party apps with tenant-wide access1020 % of apps
Agents with tenant-wide file access1050 % of agents

A component loses its weight in proportion to how far its share runs towards the cap. Only components that are Ready count; the score is rescaled to their weights, and while fewer than three are Ready the score is withheld and prints as a dash - a tenant connected an hour ago gets no flattering number from the three instant ratios alone, and no punishing one either. Grades: A from 90, B from 75, C from 60, D from 40, E below. The method is printed in every How this was measured section.

The score sits in the masthead of every report as a fixed badge: Access Exposure Score · 78 · B · powered by 1Security. A partner's brand kit can switch it to the co-branded form, Contoso Partners with 1Security. The badge stays when Mention 1Security is switched off: a white-label report keeps its branding, footer and methodology mention as you set them, but the number must say what method produced it, or an auditor cannot compare two reports from two partners. In a document over several tenants the badge carries the label and the score appears as a column of the tenant overview.

A figure a reader cannot check is a claim. Under a ready check the report prints where it came from: Open list opens the dashboard list behind the number, filtered exactly as the check reads it, and API gives the REST request (GET /api/v1/files?…) that returns the same rows, so an auditor reproduces the count without a 1Security login and a SOC platform pulls the evidence straight from the document. The dashboard link follows the Link findings to 1Security switch; the API form is always printed. The JSON format, the REST API and the MCP tools carry the same links as an evidence object on each check, with the MCP tool and arguments added. A check that is pending or not evaluated has no evidence links - it prints its reason instead.

Formats

FormatWhat you get
PDFThe laid-out document. Every page has a footer with your footer text, the confidentiality label and page numbers.
PowerPointA 16:9 deck with the same sections, wording and branding as the PDF. Text, tables and bars are ordinary slide objects, so you can edit a slide or paste it into your own deck. Long tables continue on the next slide. A PNG or JPEG logo appears on the cover; with an SVG or WebP logo the deck shows your company name instead.
HTMLOne self-contained file with no external resources. It opens in any browser and can be attached to an email.
CSVOne row per check for Copilot readiness, one row per framework and article for compliance, or one row per trend for a trends review. Every row also carries a state and a data_as_of column, so a pending or not-evaluated check is never read as a pass.
JSONThe full report document, for your own tooling.

Print prints the preview straight from the browser.

Reports Over the API

The same templates are available on the REST API with the evidence:read scope. One request returns the file itself:

curl -H "Authorization: Bearer $ONESEC_API_KEY" \
  -o readiness.pdf \
  "https://api.1security.ai/api/v1/reports/templates/builtin:copilot-readiness-briefing/render"

Add ?format=pptx, html, csv or json for the other formats. Use the ID of a saved template in place of the built-in one to get your own branding.

A tenant-bound key renders its own tenant. An organization-wide key renders the tenant you name in the X-Tenant-Id header, so a loop over your tenant list makes one call per tenant and produces one report per client.

A partner key can also ask for the whole pack in one call: POST /reports/templates/{id}/batch queues one report per client tenant, GET /reports/batches/{id} reports progress and GET /reports/batches/{id}/content returns every finished file as one ZIP.

The API reference lists the endpoints, the parameters and the per-tenant loop for partners. On the MCP server, list_report_templates and get_report return templates and report data as JSON or CSV; PDF, PowerPoint and HTML are available over REST only.

Exports From Any List

Every list in the dashboard - users, files, the files of one user, the members of a group, the activity log - has a Download button, and what it produces is a report too. Each CSV starts with a block that says what the rows are, before the column names:

LineWhat it says
TitleThe list and its subject - Files of user Jane Doe, Members of group Finance, Users.
TenantThe tenant the rows come from.
GeneratedDate and time in UTC, and who asked for the export.
SubjectThe user, file, group, site, application, label, license, location or alert the list belongs to.
LocationFor files exported from the columns view: the site, library and folders above the rows.
ScopeThis folder only or this folder and everything below.
RowsHow many rows the list had, and Part n of m when the export is split into files of 10,000 rows.
Sort and filtersThe sort order and one line per filter that was on, in words; none - the whole list otherwise.

The file is named after the same title - Files of user Jane Doe - Contoso - 2026-11-04.zip, with filtered appended when filters were on - and so is the email when you choose email delivery. The columns beneath the block are the same as before, so a spreadsheet opens the file as it always did. Column names, filter names and filter options are the ones the screen shows, in the dashboard language, because the export reads the dashboard's own translations.

Schedule this export, in the same Download dialog, puts the list on a cadence: the rows as filtered and sorted right now, exported weekly or monthly and mailed to the recipients you name, under the same title and header block as the download, so the schedule, the mail and the file all say the same thing. The schedule appears on the Schedules tab marked List export, and each file under Single reports on Generated reports, kept for 24 hours like every report. Scheduled list exports come out as CSV; the other formats are in progress and the dialog shows them greyed out. Over the API a list export schedule carries kind: export and the exportQuery it runs.

The columns view of Files has its own Download button next to the location bar. It asks what to export: the folder you are standing in, with the sort and filters you see, or that folder and everything below it. The second one lists every file in every subfolder in path order - the path column tells the subfolders apart, so one flat file holds the whole tree. Active filters still apply. The title reads Files in Finance and below, and the file is named the same way.

Good to Know

  • Shared and private copies. A copy shared with the organization is visible to every admin of the organization's tenants; a private copy only to you. You can change this on the template at any time.
  • Connected tenants are reported together. In the All tenants view of tenants connected together, one document covers all of them: a tenant overview, then a chapter per tenant. Otherwise a report covers the tenant you have open.
  • Demo tenant. Templates cannot be saved on the demo tenant. You can still customize one and download the result.
  • Files over the API are kept for 24 hours. Download a rendered file within that time, or render it again.
  • Language. The report itself is available in English, Polish, German, French, Spanish, Russian and Ukrainian. A ready-made template starts in the language of your dashboard, with regulations and articles cited the way that language cites them. A saved template keeps the language it was saved with. A trend you named yourself is printed as you named it.
  • Access. The screen is available to administrators only. For an administrator on custom permissions it is the Reports row of the permission matrix: View all opens templates and past runs, Write all also creates, edits and generates. It is granted separately from Compliance.

On this page