Sample report

anatomy of one finding.

A finding is a single record that links related cost, security and compliance signals about the same resource, then gives them one severity and one owner. This page shows an example, built for AWS and Azure teams who want to see the shape before they connect anything.

Published 16 October 2026 · Illustrative sample, not customer data.

The report card

what does a finding report contain?

Each finding names the resource, shows what was seen across cost, security and compliance, and states a severity and an owner. It then lists the evidence, a suggested fix, and a status history, so the person who owns it can act without hunting for context.

Finding · sample

Illustrative sample, not customer data

storage bucket made public, production account.

Resource: Storage bucket, production account
Severity: Critical
Owner: Platform team
Status: Open

What we saw

Cost 09:12
Spend on a storage service starts to rise for this resource.
Security 09:14
The bucket's access settings now allow public access.
Compliance 09:20
A control requiring private storage in production starts to fail.

Three signals, one cause: shown as one finding rather than three alerts.

Evidence

Billing data showing the cost change for this resource
Configuration data showing the access setting change
Audit log entry showing who changed it and when
The failing control and the resource it applies to

Suggested fix

Confirm whether public access was intended.
If not, block public access on the bucket.
Review what was reachable while it was public.
Re-check the failing control and close the finding.

A recommended fix, with owner and status tracked in OpsOne.

Status timeline

09:12 · Cost signal detected
09:14 · Security signal detected and linked to the same resource
09:20 · Compliance signal detected and linked; finding raised as Critical
Next · Owner assigned, fix recommended, status: Open

What does each field in a finding mean?

The resource says what is affected. Severity says how urgently to act. The owner is the named person accountable for the fix. Evidence shows why the finding exists, the suggested fix proposes a next step, and the status timeline records what has happened so far, so nothing is lost between teams.

Fields in a sample finding
Field	What it tells you
Resource	What is affected, and where it runs
What we saw	Cost, security and compliance signals about that resource
Severity	How urgently the finding needs attention
Owner	The named person accountable for the fix
Evidence	The billing, configuration and audit data behind the finding
Suggested fix	A recommended next step for your team to review
Status timeline	What has happened, and when

With OpsOne

how OpsOne fits in.

This sample is illustrative. In OpsOne, findings like this come from read-only access to your AWS and Azure accounts, and every finding carries a severity and a named owner. No customer data is shown on this page.

From AAIRA Technologies. About OpsOne

see your whole cloud, on one board.

Book a demo and we'll show you cost, security and compliance together across AWS and Azure. Prefer to read first? See a sample finding, or write to us.

Book a demo See a sample finding Getintouch@aaira.tech