An IRAP assessment belongs in a versioned evidence register
Record the assessed boundary and manual edition before drawing a procurement conclusion.
A procurement evidence question
An assessment announcement can be useful procurement evidence without approving every deployment of a product. The first task is to identify what was assessed, under which control edition and within which service boundary. Truthound can check a prepared evidence register against the control references supplied by the review team. It cannot perform an IRAP assessment or grant a certification.
The vendor's assessment announcement
H2O.ai announced on September 2, 2026 that H2O AI Cloud had completed an IRAP assessment against the March 2026 Information Security Manual's PROTECTED-level controls. The release is the vendor's account of that assessment. It should not be restated as blanket certification, automatic government approval or proof that every customer configuration falls within the assessed scope.
Build a scope-aware register
Create a register containing control identity, ISM edition, product component, assessed boundary, evidence reference and review state. Keep the underlying assessment material separate from the press release. A release can establish that the vendor made the announcement; a procurement reviewer may require more specific evidence before accepting a component or deployment boundary.
Check the control reference
For the assessment evidence reference table prepared as a Polars DataFrame, Truthound Core Python SDK 3.3.4's ReferentialIntegrityValidator can check whether the listed control identities appear in a supplied reference register. That catches a broken link to an obsolete or unrelated identifier. It does not establish that the evidence satisfies the control. Edition and scope must be part of the reference policy so a familiar control number is not accepted under the wrong manual.
A dataframe-based alternative
Pandera 0.35.0 is a practical alternative for an existing dataframe-based review register, including Polars. An owner-written membership predicate can retain the same approved control set, provided its construction and updates are tested. The choice is how the review team maintains references and exceptions, not which library provides stronger regulatory recognition.
Find a boundary mismatch
Review one boundary mismatch explicitly. A control may have evidence for one service component while the intended customer deployment adds another integration. Keep that row unresolved instead of borrowing the assessment status of its neighbor. This makes the register useful for asking the assessor or vendor a precise question rather than collecting a set of reassuring labels.
Keep three decisions distinct
Approve only what the authorized reviewer can support from the required evidence. Revisit the register when the manual edition, service boundary or intended integration changes. Preserve the distinction between vendor announcement, assessment evidence and the organization's own procurement decision. A structurally clean register helps trace those decisions; it does not collapse them into one approval.
Evidence
- Event checked
- Subject checked
- Modified
