Limitations
Deprecated and planned
What still works but should not be relied on, and what is genuinely not built, kept apart so neither is mistaken for the other.
Currentengine 9.0.0Verified 2026-08-30
Deprecated
Present, still functioning, and not to be built on.
| Deprecated | Replaced by | Note |
|---|---|---|
| The legacy access status field | The connection state | The old field recorded an intention. The new one records only what a real verification measured. Legacy records deriving from it are re-verified before an assessment can run, rather than being promoted silently |
| The operator-issued delivery link | The customer portal | The portal is the delivery path. The operator link remains available for exceptional cases and is not part of the automated journey |
Planned
Nothing on this page is a commitment to a date. These are known gaps, not a roadmap.
| Not built | What it would need |
|---|---|
| Peer benchmarking | A dataset with a named source, a sample size, a date and a stated methodology |
| A comparison window beyond 90 days | Moving the assessment snapshot to storage other than the workflow platform's artifacts |
| The Evidence Register issued through the portal automatically | A change to how the pack is retrieved and stored. Today the register is produced with every assessment and is available on request |
| Delivery governance as a scored domain | A separate authorization to read source control, and a scoring model published to the same standard as the three in scope |
| Independent audit of individual control results | One assessment where a reviewer walks the top findings back to the resources and confirms each |
Not planned
AI governance, compliance framework mapping, cyber insurance analysis, portfolio aggregation, continuous monitoring, and clouds other than AWS. These are not gaps awaiting work; they are outside what GovIntel is. See What GovIntel does not assess.
How to read a status label
See Status legend.