Our engineers set up and run your first AI security scan. Get in touch

GV-1.1: Legal and regulatory requirements involving AI are understood

Document applicable AI legal + regulatory obligations.

Last reviewed September 2026

Why GV-1.1 evidence is hard

In NIST AI 600-1, Legal and regulatory requirements involving AI are understood addresses govern. Document applicable AI legal + regulatory obligations. Penaxtra records this control at high severity and establishes its state by exercising it against the running system, so the result reflects observed behavior rather than a documented assertion.

How Penaxtra maps to GV-1.1

Penaxtra turns this NIST AI 600-1 obligation into recurring, testable evidence: scheduled scans and posture checks produce findings tied to GV-1.1, and the append-only audit log records what was tested and when. The NIST AI 600-1 GV-1.1 identifier is attached when the finding is created, so it appears in the exported evidence pack already mapped to the control. Where the same weakness maps to another framework, the finding carries those control identifiers as well.

GV-1.1 capabilities

Probe and check coverage aligned to GV-1.1 (Legal and regulatory requirements involving AI are understood)

Findings tagged with the NIST AI 600-1 GV-1.1 identifier

Penaxtra severity for this control (high)

Cross-framework identifiers attached to the same finding where controls overlap

PDF and JSON evidence export with the control identifier attached

GV-1.1 control coverage

Findings for GV-1.1 carry the NIST AI 600-1 GV-1.1 identifier along with the corresponding control identifiers in the other frameworks Penaxtra maps, so one result is reflected across each mapped framework.

Frequently asked

What is GV-1.1 (Legal and regulatory requirements involving AI are understood)?

Document applicable AI legal + regulatory obligations. It is a NIST AI 600-1 control; Penaxtra assesses it at high severity.

How does Penaxtra test for GV-1.1?

Penaxtra turns this NIST AI 600-1 obligation into recurring, testable evidence: scheduled scans and posture checks produce findings tied to GV-1.1, and the append-only audit log records what was tested and when.

Does a finding for GV-1.1 help with an audit?

Each finding is tagged with the NIST AI 600-1 GV-1.1 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.