A sample of what the review hands you.
Sample Utility Co. does not exist. Its people, figures and findings are invented to show the form of the report. The standard of 32 controls is real.
The result by domain
Eight domains, each with its weakest point.
A domain that is met still names where it is thinnest. The report hides nothing behind a pass.
| Domain | Controls met | Result | Main gap or weakest point |
|---|---|---|---|
| Ownership and decision rights | 2 of 4 | Partly met | No business approver for shared types |
| Ontology structure and change control | 2 of 4 | Partly met | Customer exists as two object types |
| Identity and access | 4 of 4 | Met | Leaver removal has little margin |
| Data classification and protection | 4 of 4 | Met | Retention rules miss 2 marked datasets |
| Automation and outbound actions | 2 of 4 | Partly met | No record for each message |
| Connections and data movement | 4 of 4 | Met | Write-back approvals are held in email |
| Timeliness and reliability | 3 of 4 | Partly met | No measured time budget for each hop |
| Audit, evidence and third parties | 4 of 4 | Met | Justification covers bulk export only |
A control is met at a score of 2 or 3. A domain is met when every control in it is met.
Finding 1 of 4, ranked high
The customer is modeled twice. One finding, in full.
Four findings carry the seven conditions. They are ranked by the harm each could cause.
- What we saw
The enrollment has two ontologies. Each holds a Customer object type, and the two use different primary keys. Two applications read one type, and the third reads the other. No document records why the second ontology was created.
- The evidence
An export of the ontology inventory, which the reviewers saw themselves. Interviews with the three application owners.
- Why it matters
A correction to a customer record in one model does not reach the other. Staff can act on two different answers about one customer.
- What the platform offers
One ontology can serve several teams. Projects, markings and object security policies keep their work apart. Object types can be moved between ontologies, and user edits are kept.
- The recommended action
Choose the Customer type that stays. Record the reason for each ontology that remains. Plan the move in the order the applications depend on it.
- The owner and the date
The chief data officer decides which type stays, by a stated date. The plan for the move is approved by the date the conditions are due.
For leadership
Three decisions the report asks for.
Each has a named role and a date. The reviewers design no fix.
| The decision | Who decides |
|---|---|
| Which Customer object type stays | The chief data officer, with the head of customer operations |
| Who approves a change to a shared object type for the business | The chief information officer |
| Who owns each hop in the time target for an outage notice | The head of grid operations |
How it is scored
Four scores, and the evidence each one needs.
We grade each piece of evidence. Seen: we inspected it ourselves. Shown: your staff demonstrated it. Stated: your staff told us.
| Score | What it means |
|---|---|
| 3 | The control works, and we saw the evidence ourselves. |
| 2 | The control works. It has minor gaps, or the evidence was shown and not seen. |
| 1 | The control works in places, or it is informal. It becomes a condition, with an owner and a date. |
| 0 | The control does not exist. |
The result is one of three: meets the standard, meets the standard with conditions, or does not yet meet the standard.
Where the report stops
Four things this review did not cover.
- The vendor's own infrastructure
The vendor's audit reports cover it.
- Penetration testing
Of the platform or of the network.
- The source systems
Beyond their connection to the platform.
- Compliance with a regulation
The review is against a written standard. It does not certify compliance with NERC CIP, state privacy rules or SOC 2.
Ask what yours would say.
Name the Foundry platform you want an answer on. We start with the scope.
Book a briefing James replies to you himself.