BlakSmith Governance Publication · BS-IDG-MANUAL-0.1 · Australian ISM Format
BlakSmith
Indigenous Data Governance & Sovereign Knowledge Graph

Indigenous Data Governance (IDG) Control Manual

Proposed People, Process, Technology, Assurance and Consuming-Entity Controls for CARE & FAIR Data Handling Lifecycles, Structured in the Discipline of the Australian Information Security Manual (ISM) with Maturity Scoring and Measurement Methods.

Catalogue Version
v0.1 (Provisional Draft)
Proposed Controls
68 Controls · 6 Domains
Primary Principles
CARE (2019) · FAIR (2016) · MnW (2018)
Australian Baseline
ASD ISM Sep 2026 · E8 · PSPF · AFGID
PROVISIONAL

Controls marked provisional are operator-drafted. No community governance group has directed, reviewed or endorsed them. This catalogue is not an Indigenous data sovereignty framework or product, and must not be presented as one. This manual is a vendor-neutral governance control reference using BlakSmith as a worked technical example. Self-assessment and automated evidence bundles are not certification or community endorsement.

Section 1 · Scope, Authority & Reading Guide

Using This Manual

This manual sets out proposed people, process, technology, assurance and consuming-entity controls for handling, governing, sharing and disposing of Indigenous data across its complete lifecycle. Following the discipline of the Australian Signals Directorate (ASD) Information Security Manual (ISM) and Essential Eight Maturity Model, every control has an immutable identifier (IDG-<DOMAIN>-<NNN>), explicit sensitivity applicability, a plain-language normative statement, four maturity levels (IDG-ML0 to IDG-ML3), verifiable evidence types and verified external framework crosswalks.

The manual is vendor-neutral. BlakSmith is documented throughout as a worked technical example, explicitly separating implemented controls, runnable automated checks and honest remaining gaps so no evidence ever overclaims.

Authority Tier 1 · Supreme

The Community Over Its Data

The community the data is about holds authority over collection, use, sharing, retention and destruction. It may adopt, strengthen, vary or reject any control for its own data.

Authority Tier 2 · Catalogue

Indigenous-Led Advisory Group

Only an Indigenous-led advisory group may move controls from provisional to community-endorsed through append-only decision records (ADG-YYYY-NNN).

Authority Tier 3 · Maintainer

The Operator (Yuma IT / BlakSmith)

Drafts provisional proposals, maintains verification tooling and records decisions on written instruction. Holds zero cultural authority over community knowledge.

68
Proposed IDG Controls
8
CARE & FAIR Lifecycle Stages
40
Controls w/ Automated Checks
12
Verified Framework Crosswalks
Catalogue domains and BlakSmith automated evidence coverage
CodeDomainControlsAutomated ChecksCode OnlyManual / Org
GOVGovernance and authority5212
PPLPeople12903
PRCProcess161006
TECTechnology171601
ASRAssurance5302
CONConsuming entity130013
TotalAll Domains6840127
Section 2 · CARE & FAIR Lifecycle Governance

CARE & FAIR Data Handling Lifecycle

The FAIR Guiding Principles (Findable, Accessible, Interoperable, Reusable) focus on data characteristics that support responsible discovery and reuse. The CARE Principles for Indigenous Data Governance (Collective Benefit, Authority to Control, Responsibility, Ethics) focus on people, purpose and sovereign authority. Together (“Be FAIR and CARE”), they govern every transition in the data handling lifecycle below — with CARE governing authority and protection whenever the two pull in different directions.

STAGE 01 Plan & Govern 7 controls CARE: A1 A2 A3 C1 STAGE 02 Collect & Consent 5 controls CARE: A1 A3 E1 E3 STAGE 03 Classify & Label 3 controls CARE: A3 E1 R3 STAGE 04 Store & Protect 8 controls CARE: A1 A3 E1 R1 STAGE 05 Access, Use & AI 19 controls CARE: A2 A3 C2 C3 STAGE 06 Share & Publish 10 controls CARE: A1 A3 C1 C3 STAGE 07 Retain, Return & Destroy 7 controls CARE: A1 A2 C3 E1 STAGE 08 (CROSS-CUTTING): MEASURE, AUDIT & CONTINUOUS ASSURANCE 9 controls | IDG-ML0 to ML3 Weakest-Link Maturity | Signed Ed25519 Evidence Bundles | Hash-Chained Audit Log | Community Review
Proposed IDG controls mapped across the 8-stage CARE and FAIR data handling lifecycle
Lifecycle StageGovernance ObjectiveCARE FocusFAIR FocusProposed IDG Controls
Stage 1
Plan & Govern
Establish community authority above organisational oversight, embed Aboriginal and Torres Strait Islander participation in data governance bodies, define separation of duties, and capture community data priorities and capability support needs before collection begins. A1 A2 A3 C1 E2 R1 R2 R1.3 IDG-GOV-001, IDG-GOV-004, IDG-GOV-005, IDG-PPL-001, IDG-PPL-002, IDG-PPL-012, IDG-PRC-014
Stage 2
Collect & Consent
Obtain and record free, prior and informed consent (FPIC) collectively before ingesting or creating data, uphold the right to decline, vary or withdraw consent, suspend processing immediately when new information arises, and review data stewardship and quality with the community. A1 A3 E1 E3 R1.2 IDG-GOV-003, IDG-PRC-002, IDG-PRC-005, IDG-PRC-006, IDG-PRC-016
Stage 3
Classify & Label
Attach ordered sensitivity classifications that automated systems can only raise, bind cultural protocols and Local Contexts TK/BC labels directly to every record so they travel across copies and derivatives, fail closed on existence hiding for restricted records, and maintain protocol-aware FAIR metadata. A3 E1 R3 F2 R1 R1.1 R1.2 R1.3 IDG-TEC-001, IDG-TEC-002, IDG-TEC-003
Stage 4
Store & Protect
Protect sensitive data at rest with application-level envelope encryption and in transit with verified TLS, isolate tenants at the database engine layer, keep data onshore by default, disclose sub-processors, match recipient environments to data sensitivity, and offer key custody up to community-held keys. A1 A3 E1 R1 A1.2 IDG-CON-003, IDG-PPL-005, IDG-TEC-004, IDG-TEC-005, IDG-TEC-006, IDG-TEC-009, IDG-TEC-012, IDG-TEC-013
Stage 5
Access, Use & AI
Prevent operator roles and break-glass accounts from overriding cultural protocols, require strong MFA and step-up authentication, gate joiner/mover/leaver access on vetting and cultural competency training, enforce purpose limitation, require fresh approval for secondary uses and derivatives, supply disaggregated data on community request, and ban unauthorised AI training or prompting. A2 A3 C2 C3 E1 E3 R1 A1.2 R1.1 IDG-CON-001, IDG-CON-002, IDG-CON-004, IDG-CON-007, IDG-CON-012, IDG-GOV-002, IDG-PPL-003, IDG-PPL-004, IDG-PPL-006, IDG-PPL-007, IDG-PPL-008, IDG-PPL-009, IDG-PPL-011, IDG-PRC-003, IDG-PRC-004, IDG-PRC-007, IDG-PRC-015, IDG-TEC-008, IDG-TEC-017
Stage 6
Share & Publish
Release data only under custodian-signed data sharing agreements with restrictive defaults, attach classification, protocols and labels to every export, apply sacred-site location generalisation and deceased-person presentation controls, prohibit onward sharing and re-identification, mandate community review before publication, and deliver agreed benefits and attribution. A1 A3 C1 C3 E1 E2 R1 R2 R3 R1.1 R1.2 IDG-CON-005, IDG-CON-006, IDG-CON-010, IDG-CON-011, IDG-PRC-001, IDG-PRC-008, IDG-PRC-011, IDG-PRC-012, IDG-TEC-014, IDG-TEC-015
Stage 7
Retain, Return & Destroy
Enforce agreement-bound retention limits with verified purges across primary stores and backups, enable communities to repatriate data in usable formats with protocols intact, support cryptographic erasure per custodian group, require signed destruction attestations, and notify communities promptly of any breach or cultural harm. A1 A2 C3 E1 E2 E3 R1 CARE precedence IDG-CON-008, IDG-CON-009, IDG-PRC-009, IDG-PRC-010, IDG-PRC-013, IDG-TEC-007, IDG-TEC-016
Stage 8
Measure & Assure
Operate a tamper-evident hash-chained audit log that communities can independently verify, perform independent access audits, maintain protocol-aware community data inventories, run scheduled CARE/FAIR self-assessments with community review, anchor signed automated evidence bundles to the audit chain, verify transfer logs and backup restore drills, and commission impartial partnership health checks. A2 A3 C2 C3 E1 E2 R1 F2 R1 R1.2 IDG-ASR-001, IDG-ASR-002, IDG-ASR-003, IDG-ASR-004, IDG-ASR-005, IDG-CON-013, IDG-PPL-010, IDG-TEC-010, IDG-TEC-011

Where CARE Deliberately Takes Precedence Over FAIR & Traditional Security

1. Existence Hiding vs Open Indexing (FAIR F4)

FAIR allows access control on metadata (A1.2) and does not require a public index, but no FAIR principle demands hiding that a record exists. Under IDG-TEC-003, restricted knowledge fails closed across search, counts, maps and error messages.

2. Erasure & Purge vs Persistent Metadata (FAIR A2 & ISM-0455/2151)

FAIR A2 asks metadata to outlive data, and ISM asks for key recovery and immutable backups. Under IDG-TEC-007, IDG-TEC-016 and IDG-PRC-010, communities can destroy their key and purge data; only the signed destruction attestation remains.

3. Community Approval per Use vs Open Licences (FAIR R1.1)

FAIR R1.1 expects clear usage licences for reuse. Under IDG-PRC-001 and IDG-PRC-004, reuse is never governed by a generic licence alone: every secondary use and derived dataset requires fresh community approval.

Section 3 · Maturity Model, KPIs & Continuous Assurance

How to Measure It

Measurement combines three complementary mechanisms: strict weakest-link Maturity Scoring (IDG-ML0 to IDG-ML3), stage-by-stage Operational Lifecycle KPIs, and a Three-Layer Assurance Loop linking automated technical evidence, accountable-officer self-assessment and independent community review.

3.1 Maturity Model & Strict Weakest-Link Scoring

IDG-ML0

Not Implemented

Control is absent, ad hoc, or fails to meet every element of IDG-ML1. Requires remediation before handling sensitive Indigenous data.

IDG-ML1

Documented & Applied

Written policies, registers, agreements and baseline safeguards are in place and applied consistently across datasets in scope.

IDG-ML2

Enforced & Reviewed

Technical or procedural gates enforce the control, exceptions and accesses are logged, and regular reviews verify practice.

IDG-ML3

System-Built & Community-Visible

Enforcement is automated and continuously tested per change, and the affected community can directly inspect or verify records.

  • Scope transparency: Every control whose classification levels overlap the organisation's levels_held is applicable. Marking an applicable control applicable: false requires a written reason surfaced in the audit event and community review.
  • Evidence gate: Any score above IDG-ML0 is rejected by pnpm idg:assessment unless concrete evidence is cited.
  • Weakest-link domain & overall rollup: Each domain's maturity equals its lowest applicable control, and the organisation's overall maturity equals its lowest applicable domain. A strong control never masks a weak point, while the distribution count (ML0/ML1/ML2/ML3) tracks incremental progress between cycles.

3.2 Three-Layer Assurance & Verification Workflow

LAYER 1 · CONTINUOUS TECHNICAL Automated Evidence Bundles pnpm idg:evidence runs mapped tests and verify scripts; signs with Ed25519 and anchors SHA-256 digest into the tenant hash-chained audit log. LAYER 2 · PERIODIC & TRIGGERED Self-Assessment & Attestation pnpm idg:assessment scores every domain by weakest applicable control (IDG-ML0 to ML3); accountable officer signs fixed non-certification statement. LAYER 3 · SOVEREIGN OVERSIGHT Community Review & Health Check Community records pending, accepted, queried or rejected with its own reference. Queries open reminders; impartial health checks verify practice.
Operational assurance commands, outputs and cadence
LayerCommand / MechanismWhat It Measures & ProducesCadence & Triggers
1. Automated Evidence pnpm idg:evidence --tenant <slug> --key <pem> Executes every mapped unit test & verify script, emits Ed25519-signed canonical JSON bundle (pass/fail/missing/manual/no_checks, zero record output), and records idg.evidence.recorded with SHA-256 digest into the tenant's hash-chained audit log. Every release & scheduled verification run against a seeded verification database.
2. Self-Assessment pnpm idg:assessment <file.yaml> --record --tenant <slug> Validates completeness, fixed non-certification attestation statement, domain & overall IDG-ML score, stores summary in tenant settings, appends idg.assessment.recorded to audit chain, and closes due reminders. At least every 12 months, plus on new dataset, new recipient, incident, agreement change or catalogue release.
3. Community Review & Health Check community_review status & IDG-ASR-005 Community reviews independently and records pending, accepted, queried or rejected with its own external record reference. queried or rejected re-opens reassessment reminders automatically. After every self-assessment; impartial partnership health check on community-agreed cycle.

3.3 Lifecycle Measurement Scorecard (KPIs)

Key performance indicators across all 8 CARE & FAIR data handling lifecycle stages
KPI IDMetric & FormulaIDG-ML1 TargetIDG-ML2 TargetIDG-ML3 TargetMeasurement Source
KPI-LC1
Stage 1: Plan & Govern
Datasets with nominated community authority
(Datasets with named community authority / Total Indigenous datasets) x 100%
Register exists 100% mapped before use 100% system-enforced Community authority register & custodian group graph
KPI-LC1b
Stage 1: Plan & Govern
Community data priorities actioned & reported
(Documented priorities reviewed & reported on schedule / Total recorded priorities) x 100%
Priorities requested >= 90% reviewed on cycle 100% tracked with community sign-off Governance committee minutes & priority register
KPI-LC2
Stage 2: Collect & Consent
Ingestion batches gated by valid collective FPIC
(Ingested Indigenous batches with valid FPIC record / Total batches) x 100%
Manual consent file kept 100% system-checked on ingest 100% verified against community register Ingestion ledger, consent lifecycle audit events
KPI-LC2b
Stage 2: Collect & Consent
Consent withdrawal / new-information suspension latency
Time from recorded withdrawal or new-info flag to access refusal
Within agreed SLA Same day (<= 24 hours) Immediate (automated fail-closed) Hash-chained audit log (`consent.*` events)
KPI-LC3
Stage 3: Classify & Label
Classified & protocol-labelled record completeness
(Records with valid classification + applicable protocols/labels / Total records) x 100%
Scheme & defaults set 100% classified; strictest on merge 100% raise-only enforced; synced labels Classification audit & Local Contexts sync log
KPI-LC3b
Stage 3: Classify & Label
Existence-hiding leak rate across read paths
Detected leaks of hidden records across search, counts, maps, APIs and errors
Excluded from main lists 0 leaks across read paths 0 leaks verified automatically per change Automated existence & authz verification suite
KPI-LC4
Stage 4: Store & Protect
Sensitive payloads sealed with per-custodian-group keys
(Sensitive+ payloads envelope-encrypted under group/tenant key / Total sensitive+ payloads) x 100%
Storage encryption active 100% app-level sealed incl. history 100% verified plaintext-free; community key option Encryption & RLS verify scripts, KMS/Terraform guard
KPI-LC4b
Stage 4: Store & Protect
Onshore residency & sub-processor disclosure compliance
Unapproved cross-border deployments or undisclosed sub-processors
Hosting region & list documented 0 off-region deploys (IaC guarded) 100% runtime & AI services jurisdiction-checked CDK/Terraform region guard & sub-processor register
KPI-LC5
Stage 5: Access, Use & AI
Protocol-bound operator override refusal rate
(Refused operator/break-glass/AI attempts on protocol-bound data / Total attempts) x 100%
Policy prohibits override 100% refused by central authz 100% verified per change & visible to community Authz unit tests, classification-verify, audit chain
KPI-LC5b
Stage 5: Access, Use & AI
Same-day leaver/revocation removal & training currency
(Access removed <= 24h & active users with current cultural training / Total) x 100%
Checklist & training run 100% same-day removal; dates tracked Automated SCIM deprovision + lapsed-training block SCIM audit events, training register, engagement logs
KPI-LC6
Stage 6: Share & Publish
Exports governed by active custodian-signed agreements
(Exports linked to active agreement with intact protocols / Total external exports) x 100%
Manual approval & log 100% carry protocols & watermarks 100% system-gated by agreement, scope & format Dataset package audit events & sharing reports
KPI-LC6b
Stage 6: Share & Publish
Pre-publication community review & benefit delivery
(Outputs reviewed before release & agreed benefits reported / Total outputs) x 100%
Clauses in every agreement 100% sent for review & logged Community co-interprets & verifies benefit delivery Publication review register & benefit reports
KPI-LC7
Stage 7: Retain, Return & Destroy
Timely destruction & signed attestation completion
(Expired/withdrawn datasets destroyed with signed attestation / Total due) x 100%
Procedure covers all copies 100% attested & delivered on time Key destroyed, chain-logged & verified post-restore Retention job logs, key erasure records, attestations
KPI-LC7b
Stage 7: Retain, Return & Destroy
Community breach notification SLA adherence
(Incidents notified within agreement SLA or <= 72h & never after regulators / Total) x 100%
Contacts & SLAs documented 100% logged & procedure tested Detection feeds notice; community co-reviews Incident register & cultural harm runbook logs
KPI-LC8
Stage 8: Measure & Assure
IDG Domain & Overall Maturity Level (IDG-ML0 to ML3)
Domain = min(applicable controls); Overall = min(applicable domains)
IDG-ML1 across all domains IDG-ML2 + community review active IDG-ML3 + automated evidence & health checks `pnpm idg:assessment` & audit chain (`idg.assessment.recorded`)
KPI-LC8b
Stage 8: Measure & Assure
Automated evidence pass rate & audit chain integrity
(Passing mapped checks / Total mapped checks) x 100% with 0 chain breaks
Checks run pre-release 100% pass; Ed25519 bundle anchored Verified with pinned key; monthly transfer & annual restore drills `pnpm idg:evidence` signed bundles & `audit-chain-verify`
Section 4 · Proposed Control Guidelines

ISM-Style Control Catalogue (68 Controls)

Use the interactive filter below (hidden when printing to PDF) to inspect proposed controls by domain, CARE/FAIR lifecycle stage, principle or evidence type.

Showing 68 of 68 controls
GOV

Guidelines for Governance and authority

5 proposed provisional controls in domain GOV

IDG-GOV-001 Stage 1: Plan & Govern provisional · v5 Audience: both Automated checks

Community authority over Indigenous data

Applies to: public internal sensitive protected restricted CARE A1 CARE A3 FAIR: CARE precedence

Applies to all data about Aboriginal and Torres Strait Islander peoples, communities, Country and knowledge, whatever its classification level.

Control

The organisation recognises that the community the data is about holds authority over it, acting through the people that community nominates. Decisions to collect, use, share, keep or destroy the data are made or approved by that authority, not by the organisation alone.

Rationale: Indigenous peoples have rights and interests in data about them, their Country and their knowledge. Without a named authority, the organisation that holds the data ends up deciding for the community by default.

Maturity descriptors for IDG-GOV-001
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The organisation keeps a register of which communities its Indigenous data relates to and who each community has nominated to decide about it.
IDG-ML2Every decision to collect, use, share or destroy Indigenous data has a recorded approval from the community's nominated people before it takes effect.
IDG-ML3Systems refuse an action that has no current community approval, and the community can review every decision made under its authority.

Evidence types: register, meeting_record, agreement, system_check

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: A record under a cultural protocol names its custodian groups. Only a person with an approved membership of one of those groups can open it. Membership is a relationship to the group, not a system role.

Implementation paths: packages/authz/src/classified.ts, packages/core/src/governance/authority-membership.ts

Automated checks: packages/authz/src/classified.test.ts

Honest gaps: When a custodian group has no active approved member, two owners or admins can bootstrap its first members citing a record of the group decision (never an owner or admin), and those memberships stay provisional pending community confirmation (issue #286). Once a group has an active member, only its approved members decide membership. Decisions to collect, use, share or destroy data are not all recorded as community approvals; that evidence is manual outside data sharing agreement sign-offs.

Framework crosswalks & departures (8)
  • TRUST Principles for digital repositories user-focus partial TRUST asks repositories to meet the norms of their user communities, which can include the people the data is about. It does not give anyone authority over the data. IDG gives that authority to the community the data is about.
  • Framework for Governance of Indigenous Data G1 partial The Framework asks agencies to partner with Aboriginal and Torres Strait Islander people at every stage of the data lifecycle. IDG-GOV-001 goes further on authority: the community the data is about decides, rather than sharing the decision with the organisation. The governance committees and paying partners in actions G1.2 to G1.4 are mapped to IDG-GOV-005, not to this control.
  • Framework for Governance of Indigenous Data G3.4 supports Noting where people can take part is narrower than IDG-GOV-001, which needs the community's approval at each of those points.
  • NIST Cybersecurity Framework (CSF) 2.0 no equivalent Security frameworks give authority to the organisation that holds the data. None gives it to the community the data is about.
  • Information Security Manual (ISM) no equivalent Security frameworks give authority to the organisation that holds the data. None gives it to the community the data is about.
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme no equivalent The Australian Privacy Principles protect individuals. They do not recognise collective authority over data.
  • FAIR Guiding Principles for scientific data management and stewardship no equivalent FAIR is about making data reusable. It does not say who holds authority over the data. CARE was written to fill that gap.
  • ISO/IEC 38505-1: Governance of data, application of ISO/IEC 38500 to the governance of data no equivalent ISO/IEC 38505-1 makes the organisation's governing body accountable for the organisation's use of data. None of the paraphrased entries (see crosswalk-gaps.md) gives authority to the community the data is about. IDG puts that community above the governing body for decisions about its data, and gives the governing body no cultural authority.
IDG-GOV-002 Stage 5: Access, Use & AI provisional · v3 Audience: both Automated checks

Operator roles cannot override community authority

Applies to: sensitive protected restricted CARE A3 CARE E1

Applies to any data under a cultural protocol, and to the emergency access process for all data at these levels.

Control

No system role, administrator account or emergency access procedure gives anyone access to data a community has placed under cultural protocol. Emergency access may exist for other data, but every use is logged and reviewed, and it never extends to protocol-bound material.

Rationale: If the people who run a system can read anything in it, authority over community knowledge sits with the operator. Keeping system administration and cultural authority apart is what makes community authority real.

Maturity descriptors for IDG-GOV-002
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Policy states that no operator role or emergency access process grants access to protocol-bound data.
IDG-ML2Access controls enforce the policy, and each use of emergency access on other data is logged and reviewed after the event.
IDG-ML3The refusal is tested automatically on every system change, and the community can see every attempt to use an operator role or emergency access against its data.

Evidence types: policy, configuration, system_check, audit_log

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: The custodian check runs before clearance. The tenant owner role does not satisfy it, and a break-glass claim is refused for protocol-bound material. Break-glass use on other material is recorded at high severity.

Implementation paths: packages/authz/src/classified.ts, docs/indigenous-data-sovereignty.md

Automated checks: packages/authz/src/classified.test.ts, @blaksmith/graph classification-verify

Honest gaps: Once a custodian group has an active approved member, only its members decide membership and owners or admins cannot add themselves. An empty group is bootstrapped by two different owners or admins citing the same group decision (never making an owner or admin a member), so initial group setup remains operator-mediated until issue #286 is resolved. The database owner connection is not subject to application-level access checks.

Framework crosswalks & departures (8)
  • NIST SP 800-53 Rev. 5 AC-3(10) exceeds AC-3(10) audits an override of access control. IDG allows no override for protocol-bound data.
  • Information Security Manual (ISM) ISM-1611 exceeds Break glass is allowed when normal authentication cannot be used. IDG never allows it for protocol-bound data.
  • Information Security Manual (ISM) ISM-1613 partial Logging of break glass use. IDG also requires review after each use.
  • NIST SP 800-53 Rev. 5 AC-5 supports
  • NIST Cybersecurity Framework (CSF) 2.0 PR.AA-05 supports
  • Information Security Manual (ISM) ISM-1508 exceeds The ISM limits privileged access to what a person's duties need. IDG bars every operator role from protocol-bound material, whatever its duties.
  • Information Security Manual (ISM) ISM-1610 partial Documents and tests emergency access. IDG also bars it from protocol-bound material and reviews every use.
  • ISO/IEC 38505-1: Governance of data, application of ISO/IEC 38500 to the governance of data no equivalent ISO/IEC 38505-1 has the governing body direct the organisation's use of data. IDG-GOV-002 sets a limit none of the paraphrased entries sets: whatever the governing body directs, no system role or emergency access reaches material a community has placed under cultural protocol.
IDG-GOV-003 Stage 2: Collect & Consent provisional · v1 Audience: both Code paths (no checks)

Right to decline and to withdraw

Applies to: public internal sensitive protected restricted CARE A1 CARE E3
Control

A community may decline to take part in any data activity and may withdraw its agreement later. When it withdraws, the organisation stops the activity, records the decision and carries out the return or destruction terms agreed with the community.

Rationale: Communities keep the right not to take part in data processes that do not meet their expectations. A right to withdraw that cannot be acted on is not a right.

Maturity descriptors for IDG-GOV-003
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Agreements state the right to decline and to withdraw, and the community has been told how to use it.
IDG-ML2A withdrawal stops new use within an agreed time, and the organisation records what was stopped, returned or destroyed.
IDG-ML3Systems stop use as soon as a withdrawal is recorded, and the return or destruction terms cover derived data and copies held by others.

Evidence types: agreement, procedure, audit_log, attestation

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Consent on a record can be revoked, and revocation is recorded as an event. Agreements record whether data is returned, destroyed or kept under protocol at the end.

Implementation paths: packages/graph/src/consent-lifecycle.ts, packages/core/src/governance/agreement.ts

Honest gaps: No automated test covers consent revocation. The return or destroy term is recorded but not carried out by the product, and copies held by others are out of its reach.

Framework crosswalks & departures (1)
  • NIST SP 800-53 Rev. 5 PT-4(3) partial Covers an individual revoking consent, not a community withdrawing collectively.
IDG-GOV-004 Stage 1: Plan & Govern provisional · v2 Audience: both Manual / Organisational

Governing body oversight below community authority

Applies to: public internal sensitive protected restricted CARE R1 CARE A3

The governing body is the organisation's board, owners, partners or executive managers, whichever governs the organisation.

Control

The organisation's governing body evaluates, directs and monitors how the organisation handles Indigenous data, and is accountable for it. It does this within the decisions of the communities the data is about. It cannot approve a use a community has not approved, and it holds no cultural authority over material a community has placed under protocol.

Rationale: Someone at the top of the organisation must answer for how it handles Indigenous data. If that oversight is not placed below community authority, the governing body ends up deciding for communities by default.

Maturity descriptors for IDG-GOV-004
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The governing body has assigned oversight of Indigenous data to itself or one of its committees, and receives a report on it at least once a year.
IDG-ML2The governing body sets its direction for Indigenous data in writing and receives regular reports on agreements, incidents, access reviews and community decisions. Its records show it has not approved anything a community has not.
IDG-ML3The governing body gets independent assurance, such as an audit, on how Indigenous data is handled, and tells the communities concerned what it found and did.

Evidence types: policy, meeting_record, report

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (5)
  • ISO/IEC 38505-1: Governance of data, application of ISO/IEC 38500 to the governance of data edm-model partial ISO/IEC 38505-1 gives the governing body the tasks of evaluating, directing and monitoring the use of data. IDG adds that it does so within the communities' decisions and holds no cultural authority.
  • ISO/IEC 38505-1: Governance of data, application of ISO/IEC 38500 to the governance of data governing-body-accountability supports
  • ISO/IEC 38505-1: Governance of data, application of ISO/IEC 38500 to the governance of data oversight-mechanisms supports
  • ISO/IEC 38505-1: Governance of data, application of ISO/IEC 38500 to the governance of data oversight-assurance supports Covers independent assurance at ML3. IDG also tells the communities concerned what it found.
  • Framework for Governance of Indigenous Data no equivalent The Framework's monitoring and accountability section mentions senior executive oversight, but it has no numbered actions, so there is no entry to map to. G1.3 covers the mechanisms for implementing the Framework, with Aboriginal and Torres Strait Islander representation, and is mapped to IDG-GOV-005, not the governing body's own oversight. IDG-GOV-004 also places that oversight below the communities' decisions.
IDG-GOV-005 Stage 1: Plan & Govern provisional · v1 Audience: both Manual / Organisational

Aboriginal and Torres Strait Islander people in data governance

Applies to: public internal sensitive protected restricted CARE E2 CARE A3
Control

Aboriginal and Torres Strait Islander people take part, with authority to influence the outcome, in the organisation's committees and other bodies that make or advise on decisions about Indigenous data. Where possible they are connected to the communities the data is about. The organisation names a person to lead its governance of Indigenous data, preferably an Aboriginal or Torres Strait Islander person, and pays people from outside the organisation for their time and expertise.

Rationale: Decisions about Indigenous data made without Aboriginal and Torres Strait Islander people repeat the exclusion that much of the data reflects. Taking part in the organisation's bodies is not the same as a community's authority over its own data: this control adds to IDG-GOV-001 and does not replace it, and no member speaks for a community unless that community says so.

Maturity descriptors for IDG-GOV-005
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The organisation names a lead for its governance of Indigenous data and records which of its bodies make or advise on decisions about that data.
IDG-ML2Those bodies include Aboriginal and Torres Strait Islander members whose views are recorded. Members from outside the organisation are paid for their time.
IDG-ML3Aboriginal and Torres Strait Islander members can put matters on the agenda and refer a decision to the community concerned, and the arrangement is reviewed with them.

Evidence types: register, meeting_record, policy

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (4)
  • Framework for Governance of Indigenous Data G1.2 partial The Framework asks each agency to set up governance mechanisms with Aboriginal and Torres Strait Islander partners to oversee its actions. IDG asks for their part in every body that decides or advises about Indigenous data.
  • Framework for Governance of Indigenous Data G1.3 partial Items a and b of G1.3 cover part of this control: representation from Aboriginal and Torres Strait Islander stakeholders as connected as possible to affected communities, with appropriate authority to influence agency actions. IDG adds their part in every body that decides or advises about Indigenous data, a named lead and paying people from outside the organisation. Items c to e, such as spanning all the organisation's data holdings and its senior executives, are not part of this control.
  • Framework for Governance of Indigenous Data G4.1(a) partial The Framework's Indigenous data champion, who would preferably be an Aboriginal or Torres Strait Islander staff member at executive level, covers part of this control. IDG adds Aboriginal and Torres Strait Islander people in governance bodies and paying people from outside the organisation. IDG prefers that its named lead be an Aboriginal or Torres Strait Islander person, but does not require executive level, the appropriate authority and support to influence the work of the agency that G4.1(a) asks for, or making upskilling and recruiting for the role a priority.
  • Framework for Governance of Indigenous Data G1.4 supports Covers paying partners for their time and expertise.
PPL

Guidelines for People

12 proposed provisional controls in domain PPL

IDG-PPL-001 Stage 1: Plan & Govern provisional · v1 Audience: both Automated checks

Defined roles and separation of duties

Applies to: sensitive protected restricted CARE A3 CARE R1
Control

The organisation names the roles that handle Indigenous data and writes down what each may do: data steward at the receiving organisation, key custodian, platform operator and auditor. For community data custodians and delegates, it records the duties the community sets for them. No one person holds roles whose duties should check each other for the same data, such as operating the platform and recording custodian appointments, or holding keys and auditing their use.

Rationale: When one person can grant access, use it and review it, mistakes and misuse go unseen. Naming the roles also makes clear that running a system is a different job from holding authority over the data in it.

Maturity descriptors for IDG-PPL-001
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The roles are written down, each with its duties, and the people in each role are known.
IDG-ML2Conflicting roles are kept apart, and any exception is approved, recorded and reviewed.
IDG-ML3Systems enforce the separation, and the community can see who holds each role for its data.

Evidence types: policy, register, configuration, system_check

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: System roles (owner, admin, editor, agent, viewer) are separate from custodian authority. Custodian-bound material needs membership of a named custodian group, and no system role substitutes for it. Classification and consent changes are limited to human owners and admins. A custodian group's members decide its membership; a tenant role neither grants nor removes that, so owners and admins who are not members cannot. Platform-wide tenant lifecycle actions need a person listed as a platform administrator by the deployment, which no tenant role grants.

Implementation paths: packages/authz/src/authz.ts, packages/authz/src/classified.ts

Automated checks: packages/authz/src/classified.test.ts, packages/authz/src/authz.test.ts, @blaksmith/graph classification-verify

Honest gaps: There are no auditor, key custodian, delegate or data steward roles in the application. The same tenant owner or admin can manage classification and administer the tenant, so separating those duties is a matter of policy, not enforcement. Two operators together can record a group's first members, pending issue #286.

Framework crosswalks & departures (3)
  • NIST Cybersecurity Framework (CSF) 2.0 GV.RR-02 partial Roles are set by the organisation. IDG adds duties set by the community for custodians and delegates.
  • NIST Cybersecurity Framework (CSF) 2.0 PR.AA-05 partial Separation of duties within access permissions only.
  • NIST SP 800-53 Rev. 5 AC-5 partial Separation of duties within systems. IDG also separates operating the platform from recording custodian appointments.
IDG-PPL-002 Stage 1: Plan & Govern provisional · v1 Audience: both Automated checks

Custodian appointments and revocations come from the community

Applies to: public internal sensitive protected restricted CARE A1 CARE A3
Control

The community decides who may act as a custodian or delegate for its data, what each may do, and when that ends. Custodian authority is never inferred from a job title, a system role, an employment relationship or seniority in the organisation. The organisation records each appointment and revocation as the community makes it, and acts on a revocation the same day.

Rationale: Authority to make decisions about Indigenous data belongs to the community. If an organisation decides who counts as a custodian, it has taken that authority for itself.

Maturity descriptors for IDG-PPL-002
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Each appointment and revocation in the register kept under IDG-GOV-001 is traceable to an instruction from the community.
IDG-ML2Appointments and revocations take effect only on a recorded instruction from the community, and revocations take effect the same day.
IDG-ML3The community, through people it chooses, makes appointments and revocations directly in the system, and the organisation cannot change them on its own.

Evidence types: register, meeting_record, audit_log, system_check

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Custodian authority is a MEMBER_OF relationship to a traditional owner group or prescribed body corporate. Only an active, approved membership grants custody. Each change is versioned and written to the hash-chained audit log, and a person cannot approve their own membership. Once a group has an approved member who can act (signed in and still a member of the tenant), only its approved members approve, reject or remove members, whatever their tenant role; a tenant owner or admin who is not a member cannot, and every decision needs a fresh step-up. A group with nobody able to act is set up, or set up again, by two different owners or admins citing the same record of the group decision, one person at a time and never an owner or admin; those memberships are marked provisional and listed in the group's reports. Deleting the relationship, the person or the group, or merging them, cannot take an approved membership away. SCIM group names and patches that try to map custodian authority are rejected, so it cannot come from an identity provider group.

Implementation paths: packages/core/src/governance/authority-membership.ts, packages/authz/src/membership.ts, packages/graph/src/service.ts, packages/auth/src/scim-groups.ts

Automated checks: packages/authz/src/membership.test.ts, @blaksmith/graph membership-verify, packages/auth/src/scim-groups.test.ts, @blaksmith/graph classification-verify

Honest gaps: The first members of a group are recorded by two operators citing the group's decision, not by the community in the system; how the community confirms them is open (issue #286), so they stay provisional. There is no distinction between a custodian and a delegate, membership has no expiry or review date, and removing a user through SCIM does not remove their custodian memberships, though it stops them counting as a member who can decide.

Framework crosswalks & departures (2)
  • NIST SP 800-53 Rev. 5 AC-2 supports AC-2 has the organisation approve accounts. IDG requires the community to make custodian appointments.
  • Information Security Manual (ISM) no equivalent Security frameworks give authority to the organisation that holds the data. None gives it to the community the data is about.
IDG-PPL-003 Stage 5: Access, Use & AI provisional · v2 Audience: consumer Manual / Organisational

Cultural competency and data sovereignty training before access

Applies to: internal sensitive protected restricted CARE R1 CARE E1

The 12 month refresh is an operator suggestion. A community may set a different interval or its own content.

Control

The organisation's staff and contractors who will handle Indigenous data complete training in cultural competency and Indigenous data sovereignty before they are given access, and refresh it at least every 12 months or sooner if the community asks. Training covers the community's expectations, the agreements that apply, and what to do if something goes wrong. What a community expects of its own custodians and delegates is for the community to decide.

Rationale: People cannot respect protocols they do not know about. Much of the harm communities experience from data comes from people who did not understand what they were holding.

Maturity descriptors for IDG-PPL-003
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Training exists, and people complete it before they get access to Indigenous data.
IDG-ML2Completion and refresh dates are recorded, and access is removed when training lapses.
IDG-ML3Training is designed or delivered with Aboriginal and Torres Strait Islander people, is specific to the communities whose data is held, and lapsed training blocks access automatically.

Evidence types: training_record, register, procedure

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (7)
  • Information Security Manual (ISM) ISM-0252 partial Cyber security awareness only, not cultural competency.
  • Protective Security Policy Framework (PSPF) 24 partial Security awareness only, not cultural competency.
  • NIST Cybersecurity Framework (CSF) 2.0 PR.AT-01 partial Cyber security awareness only, not cultural competency or data sovereignty.
  • NIST SP 800-53 Rev. 5 AT-2 partial Security and privacy literacy only, not cultural competency.
  • NIST SP 800-53 Rev. 5 AT-3 supports
  • Framework for Governance of Indigenous Data G2.1(b) partial The Framework's cultural competence training covers part of this control. IDG adds training before access, a refresh at least every 12 months and the agreements that apply. The Framework also asks that the training be by an Aboriginal and Torres Strait Islander-owned and appropriate training organisation, which IDG-PPL-003 does not require.
  • Framework for Governance of Indigenous Data G2.3 supports The Framework asks for Indigenous data concepts, including BADDR data, to be built into staff data training. IDG-PPL-003 covers Indigenous data sovereignty but does not name those concepts.
IDG-PPL-004 Stage 5: Access, Use & AI provisional · v1 Audience: consumer Manual / Organisational

Vetting and suitability

Applies to: sensitive protected restricted CARE E1

Checks should be proportionate, with the most thorough checks at the higher levels.

Control

The organisation's staff and contractors who handle sensitive Indigenous data pass its existing pre-employment and ongoing suitability checks, at a level that matches the sensitivity of the data. A community may ask for further requirements for its own data, and the organisation meets them or does not give that person access. Suitability of a community's own custodians and delegates is for the community to decide.

Rationale: Organisations already run personnel security for sensitive information. Indigenous data deserves at least the same care, without building a separate process that duplicates it.

Maturity descriptors for IDG-PPL-004
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The organisation's existing personnel checks are applied to everyone with access to Indigenous data at these levels.
IDG-ML2Checks are repeated on a set cycle, and any community requirements are recorded and met before access is given.
IDG-ML3Access is tied to current suitability, so it is suspended automatically when a check lapses or is failed.

Evidence types: policy, register, procedure

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (5)
  • Information Security Manual (ISM) ISM-0434 partial Screening before access only. IDG adds ongoing checks and requirements set by the community.
  • Protective Security Policy Framework (PSPF) 116 partial IDG adds requirements set by the community for its own data.
  • Protective Security Policy Framework (PSPF) 164 supports
  • NIST SP 800-53 Rev. 5 PS-3 partial IDG adds requirements set by the community for its own data.
  • NIST Cybersecurity Framework (CSF) 2.0 GV.RR-04 supports
IDG-PPL-005 Stage 4: Store & Protect provisional · v1 Audience: both Automated checks

Key custodians

Applies to: sensitive protected restricted CARE A1 CARE A3
Control

Only named key custodians can carry out actions on encryption keys that protect Indigenous data, such as disabling, rotating or destroying a key. Key custodians use multi-factor authentication, are separate from day-to-day platform operators, record a reference and reason for each action, and act on a destruction or withdrawal request from the community within the time agreed with the community.

Rationale: Whoever controls the keys controls whether data can be read or destroyed. Those actions must be deliberate, attributable and responsive to the community.

Maturity descriptors for IDG-PPL-005
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Key custodians are named, and key actions are limited to them by policy.
IDG-ML2Key actions need multi-factor authentication and a recorded reference and reason, and every action is logged.
IDG-ML3Key actions are enforced by the key service itself, each one is written to a tamper-evident record the community can see, and the community can hold its own key.

Evidence types: register, configuration, audit_log, procedure

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: The AWS Terraform defines a key custodian role that can only be assumed with multi-factor authentication. The application data key's policy denies disabling and scheduling deletion of that key to roles outside the key custodian name prefix. The custodian key erasure script requires a reference, a justification and typed confirmation of the group being erased. A unit test shows that erasing one custodian group's key, with the local provider, makes only that group's data unreadable. Communities can hold their own key under the documented community-held key option.

Implementation paths: infra/aws/terraform/kms.tf, infra/aws/scripts/erase-custodian-key.sh, docs/key-custody.md

Automated checks: packages/crypto/src/crypto.test.ts

Honest gaps: The deny applies only to the application data key, not to the database, storage, log or per-group keys. Any role whose name starts with the key custodian prefix is exempt, whether or not it needs multi-factor authentication, and the account root can rewrite the key policy. The custodian role can schedule deletion of the application key, which protects every tenant, but its policy does not cover the per-group keys the erasure script targets. There is no key custodian role or erasure path in the application. The script checks the caller with a substring match and prints its record without writing it to the audit log. Nothing tests the Terraform or the script, and no live erasure or cross-account drill has been run.

Framework crosswalks & departures (3)
  • NIST SP 800-53 Rev. 5 SC-12 partial Key management in general. IDG adds named custodians, separation from operators and acting on community requests.
  • NIST SP 800-53 Rev. 5 SA-9(6) supports
  • Information Security Manual (ISM) ISM-0507 partial Key management procedures. IDG adds named custodians and acting on community requests.
IDG-PPL-006 Stage 5: Access, Use & AI provisional · v1 Audience: both Automated checks

Strong authentication for privileged and custodian roles

Applies to: sensitive protected restricted CARE E1
Control

Anyone with administrative, custodian or key custody duties signs in with phishing-resistant multi-factor authentication. Actions that change who can see Indigenous data, or how it is classified, need a fresh authentication at the time.

Rationale: Stolen and guessed passwords are a common way into systems, and privileged accounts are where a stolen password does the most harm.

Maturity descriptors for IDG-PPL-006
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Multi-factor authentication is required for administrative and custodian accounts.
IDG-ML2Sensitive actions need authentication within the last few minutes, and API keys cannot perform them.
IDG-ML3Phishing-resistant methods such as passkeys are required, and remembered devices cannot skip them.

Evidence types: configuration, system_check, audit_log

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Users can enrol TOTP and passkeys, with user verification required for passkeys. When BLAKSMITH_REQUIRE_MFA is enabled (the default in production), owners, admins and platform admins are held at two-factor enrolment before accessing protected surfaces. Classification, consent, sharing-term and all custodian membership decisions (approve, reject and remove) need a fresh step-up from TOTP or a passkey in the same session within the last five minutes, and API keys never carry step-up.

Implementation paths: packages/auth/src/auth.ts, packages/auth/src/mfa-enrolment.ts, packages/auth/src/principal.ts, packages/authz/src/classified.ts

Automated checks: packages/auth/src/step-up.test.ts, packages/auth/src/mfa-enrolment.test.ts, packages/authz/src/classified.test.ts

Honest gaps: Multi-factor authentication is not enforced for non-admin custodian members, editors or viewers, and federated SSO sessions rely on the identity provider. Trusting a device for 30 days skips TOTP. Phishing-resistant passkeys are optional rather than required, and there is no inline prompt to step up at the moment of a sensitive action, so the five minute window usually means a recent sign-in.

Framework crosswalks & departures (6)
  • Information Security Manual (ISM) ISM-1173 partial MFA for privileged users. IDG also requires re-authentication for sensitive actions.
  • Information Security Manual (ISM) ISM-1682 partial Phishing-resistant MFA. IDG also requires re-authentication for sensitive actions.
  • Information Security Manual (ISM) ISM-1504 supports
  • NIST SP 800-53 Rev. 5 IA-11 partial Re-authentication in organisation-defined circumstances. IDG names the sensitive actions.
  • Essential Eight Maturity Model Multi-factor authentication partial The Essential Eight requires MFA, and phishing-resistant MFA at higher maturity levels. IDG adds re-authentication for sensitive actions.
  • NIST Cybersecurity Framework (CSF) 2.0 PR.AA-03 supports
IDG-PPL-007 Stage 5: Access, Use & AI provisional · v2 Audience: consumer Automated checks

Joiners get the least access they need, once approved

Applies to: internal sensitive protected restricted CARE A3 CARE E1
Control

A new member of the organisation's staff or contractors gets access to Indigenous data only after their role is approved, they have completed the required training and checks, and they have agreed in writing to the conditions that apply. They get the least access their role needs, and access to protocol-bound data only through the community's own appointment.

Rationale: Access given by default, or more broadly than needed, makes misuse easier and harder to notice.

Maturity descriptors for IDG-PPL-007
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Access requests are approved by a named person and recorded.
IDG-ML2Access is granted only after training, checks and signed conditions are recorded, and starts at the least privileged role.
IDG-ML3Provisioning is automated from an approved source, and access to each community's data needs that community's appointment.

Evidence types: procedure, register, configuration, audit_log

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Users can be provisioned through SCIM, where groups map to exactly one role and a missing or conflicting mapping means no access. An accepted organisation invitation starts at the viewer role, and the signed-in email must match the invitation.

Implementation paths: packages/auth/src/scim-groups-db.ts, packages/auth/src/organisation-collaboration.ts

Automated checks: packages/auth/src/scim-groups-db.test.ts

Honest gaps: The product does not record training, checks or signed conditions. Invitations need no step-up, any email address can be invited, and an invited viewer has open-ended access. No automated test covers the viewer default for accepted invitations.

Framework crosswalks & departures (7)
  • Information Security Manual (ISM) ISM-0405 partial Validation of access requests. IDG adds training, checks and signed conditions first.
  • Information Security Manual (ISM) ISM-1852 partial Least privilege. IDG adds approval, training and community appointment for protocol-bound data.
  • Essential Eight Maturity Model Restrict administrative privileges supports
  • NIST SP 800-53 Rev. 5 AC-2 partial Account approval by the organisation. IDG adds training and signed conditions.
  • NIST SP 800-53 Rev. 5 AC-6 partial Least privilege only.
  • NIST SP 800-53 Rev. 5 PS-6 supports
  • Information Security Manual (ISM) ISM-1508 partial Least privilege for privileged access. IDG adds approval, training and community appointment for protocol-bound data.
IDG-PPL-008 Stage 5: Access, Use & AI provisional · v1 Audience: both Automated checks

Movers have their access reviewed

Applies to: internal sensitive protected restricted CARE E1
Control

When a person changes role, team or project, their access to Indigenous data is reviewed and reduced to what the new role needs when the change takes effect. Access they no longer need is removed, not left in place.

Rationale: People who move inside an organisation tend to collect access over time. Each move is the natural point to take back what is no longer needed.

Maturity descriptors for IDG-PPL-008
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Role changes trigger a manual access review, and the outcome is recorded.
IDG-ML2Access is adjusted on the day of the change, and existing sessions are ended.
IDG-ML3Role changes flow from an authoritative source, access is re-derived automatically, and a periodic review catches anything missed.

Evidence types: procedure, register, audit_log, system_check

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.); accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: When SCIM group membership changes, the user's role is re-derived from the mapped groups and their sessions are revoked immediately, and conflicting mappings mean no access. For users outside SCIM, an owner or admin with step-up can change another member's role.

Implementation paths: packages/auth/src/scim-groups-db.ts

Automated checks: packages/auth/src/scim-groups.test.ts, packages/auth/src/scim-groups-db.test.ts

Honest gaps: Nothing prompts an access review when someone moves. Custodian memberships and consultant engagements are not reviewed when a role changes.

Framework crosswalks & departures (2)
  • NIST SP 800-53 Rev. 5 PS-5 partial The organisation sets the actions and timing. IDG requires review when the change takes effect.
  • NIST Cybersecurity Framework (CSF) 2.0 PR.AA-05 supports
IDG-PPL-009 Stage 5: Access, Use & AI provisional · v2 Audience: both Automated checks

Leavers and project ends remove access promptly

Applies to: internal sensitive protected restricted CARE A3 CARE E1
Control

When a person leaves, or a project or engagement ends, all their access to Indigenous data is removed by the end of that day. This covers accounts, sessions, API keys, key custody duties, custodian appointments made for that role, and any copies of data they hold, which are returned or destroyed under the agreement.

Rationale: Former staff and finished projects are a common source of data that leaks long after anyone remembers it was shared.

Maturity descriptors for IDG-PPL-009
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1A leaver checklist covers every kind of access and every copy, and is completed for each leaver and project end.
IDG-ML2Access is removed on the last day, and the removal is recorded and checked.
IDG-ML3Removal is automatic from an authoritative source, including sessions and API keys, and the community is told when someone with access to its data leaves.

Evidence types: procedure, register, audit_log, attestation

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: SCIM deprovisioning deletes the user's tenant-bound API keys, tenant membership, organisation and team rows, federated identities and all sessions in one transaction. A consultant or proponent engagement refuses access once it expires, whatever roles remain.

Implementation paths: packages/auth/src/scim-groups-db.ts, packages/auth/src/scim-users.ts, packages/graph/src/engagement.ts, packages/authz/src/classified.ts

Automated checks: packages/auth/src/scim-groups-db.test.ts, packages/auth/src/scim-users.test.ts, packages/authz/src/classified.test.ts

Honest gaps: Deprovisioning leaves historical custodian membership and engagement records in place (though the user can no longer act in a custodian group without a tenant membership). Key custodian privileges held outside the application are not touched. Users who were not provisioned through SCIM cannot be removed in the application. Engagement expiry refuses access but does not end sessions or remove roles. The product does not track the return or destruction of copies.

Framework crosswalks & departures (6)
  • Information Security Manual (ISM) ISM-0430 partial Same day removal of system access. IDG adds return or destruction of copies and ending custodian and key duties.
  • Information Security Manual (ISM) ISM-1845 supports
  • Protective Security Policy Framework (PSPF) 186 partial Access withdrawn on separation. IDG adds project end and return or destruction of copies.
  • NIST SP 800-53 Rev. 5 PS-4 partial Termination only, not project end.
  • Information Security Manual (ISM) ISM-1404 supports Disables unprivileged access after 45 days of inactivity. IDG removes access when a person leaves or a project ends.
  • Information Security Manual (ISM) ISM-1648 supports Disables privileged access after 45 days of inactivity. IDG removes access when a person leaves or a project ends.
IDG-PPL-010 Stage 8: Measure & Assure provisional · v5 Audience: both Automated checks

Independent audit of access, visible to the community

Applies to: sensitive protected restricted CARE A2 CARE R1
Control

Someone independent of the people who operate the platform reviews access to Indigenous data on a set cycle. The community can see who accessed its data, when and for what stated purpose, including refused attempts and any emergency access.

Rationale: People who run a system should not be the only ones checking how it is used. Communities cannot hold anyone to account for access they cannot see.

Maturity descriptors for IDG-PPL-010
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Access logs are kept and reviewed by someone other than the platform operators at least once a year.
IDG-ML2The review is at least quarterly, and the community receives a report of access to its data.
IDG-ML3The community can see access to its data at any time, from a log that cannot be changed without detection.

Evidence types: audit_log, report, meeting_record

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Access to custodian-bound records is written to a hash-chained audit log. The governance worker can publish a per-custodian-group access report, including refused reads, emergency access and unusual activity, with an anchored digest of the log.

Implementation paths: packages/graph/src/access-transparency.ts, packages/graph/src/audit-chain.ts, packages/discovery/src/governance-worker.ts

Automated checks: @blaksmith/discovery governance-verify, @blaksmith/graph audit-chain-verify

Honest gaps: There is no auditor role and no in-app view of the report for the community. Reports are only written when the operator sets an export directory, and the operator decides how they reach the community. Reports select past access by each record's current custodian group, so if custody changes, earlier access can drop out of the original community's report or appear in the new group's.

Framework crosswalks & departures (8)
  • NIST SP 800-53 Rev. 5 CA-7(1) partial Independent assessment, but not visibility to the community.
  • NIST SP 800-53 Rev. 5 AU-6 partial Audit review by the organisation, not reporting to the community.
  • NIST SP 800-53 Rev. 5 AU-9 supports
  • Information Security Manual (ISM) ISM-1815 supports
  • TRUST Principles for digital repositories transparency supports The community can see who accessed its data. This record goes to the community, not the public.
  • Framework for Governance of Indigenous Data G3 partial The Framework's ask that people can know how data about their interests is used covers part of this control. IDG adds independent review on a set cycle, and shows the community who accessed its data, when and for what stated purpose, including refused attempts and emergency access. G3 also asks that people know what data is held and how to access it, which no IDG control requires (see crosswalk-gaps.md).
  • ISO/IEC 38505-1: Governance of data, application of ISO/IEC 38500 to the governance of data oversight-assurance supports The governing body gets assurance through audit and independent assessment. IDG-PPL-010 also makes the record of access visible to the community.
  • Information Security Manual (ISM) ISM-0414 supports Unique user identification is what lets the community see who accessed its data.
IDG-PPL-011 Stage 5: Access, Use & AI provisional · v2 Audience: both Automated checks

Outside parties have time-limited, purpose-limited access

Applies to: internal sensitive protected restricted CARE A3 CARE E1
Control

Consultants, contractors, proponents and other outside parties get access to Indigenous data only for a stated purpose and a fixed period, sponsored by a named person in the organisation. Access ends automatically at the end of that period, and outside parties cannot take away precise or culturally restricted material.

Rationale: Outside parties are often given access for one job and keep it long after. Their copies are also the hardest for a community to trace.

Maturity descriptors for IDG-PPL-011
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Each outside party's access has a sponsor, a purpose and an end date on record.
IDG-ML2Access is refused after the end date and outside the stated purpose, outside parties cannot export precise or culturally restricted material, and permitted exports are marked with who made them.
IDG-ML3The community approves each outside party's access to its data, and is told when it starts and ends.

Evidence types: register, agreement, configuration, audit_log

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: A consultant or proponent engagement has an end date, permitted purposes and a sponsor, and writes to engagement records are gated by authoriseEngagementWrite. Engagements are looked up directly by principal with no row cap, and a missing, malformed, unreadable or ambiguous engagement fails closed into a locked-out state. Access is refused after the end date whatever roles remain, and refused for a stated purpose outside the engagement's purposes. A proponent without custody is not shown existence-hidden material. Consultants cannot export culturally bound or encrypted material, and permitted exports are watermarked.

Implementation paths: packages/graph/src/engagement.ts, packages/authz/src/classified.ts

Automated checks: packages/graph/src/engagement.test.ts, packages/authz/src/classified.test.ts

Honest gaps: The purpose limit applies only when a request states a purpose. The engagement's custodian group is used only in the watermark, and the community does not approve engagements directly in the product.

Framework crosswalks & departures (4)
  • NIST SP 800-53 Rev. 5 PS-7 partial Personnel security for external providers. IDG adds a fixed end, stated purposes and export limits.
  • NIST Cybersecurity Framework (CSF) 2.0 GV.SC-07 supports
  • Protective Security Policy Framework (PSPF) 75 partial Need-to-know for people outside the entity. IDG adds a fixed end and export limits.
  • Information Security Manual (ISM) ISM-0441 partial Restricts temporary access to the data needed. IDG adds a named sponsor, a fixed period that ends automatically, and no taking away precise or culturally restricted material.
IDG-PPL-012 Stage 1: Plan & Govern provisional · v1 Audience: both Manual / Organisational

Support for community data capability, on the community's terms

Applies to: public internal sensitive protected restricted CARE R2 CARE C1
Control

Where a community wants it, the organisation supports the community to build the data capability it chooses, such as data literacy, skills, people and infrastructure to manage and govern its own data. The community decides whether it wants support, what kind and from whom. The organisation pays for the support it offers, and never makes it a condition of the community's authority over its data.

Rationale: CARE asks those who use Indigenous data to enhance data literacy in communities and support an Indigenous data workforce and infrastructure. Without that capability, a community's authority over its data is harder to use. Support that comes with conditions would become leverage over the community.

Maturity descriptors for IDG-PPL-012
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The organisation asks each community it holds data about whether it wants data capability support, and records the answer.
IDG-ML2Support a community asks for is planned with it, paid for and delivered, and the community reviews whether it met its needs.
IDG-ML3Support includes things the community keeps, such as its own infrastructure, trained people or tools, and the organisation checks with the community whether its capability has grown.

Evidence types: register, agreement, report, meeting_record

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (4)
  • Framework for Governance of Indigenous Data G2.6 partial The Framework asks agencies to strengthen the data capability of Aboriginal and Torres Strait Islander Community Controlled Organisations and other stakeholders. IDG leaves whether and how to the community.
  • Framework for Governance of Indigenous Data G2 supports Guideline 2 asks, among other things, to improve the capabilities of Aboriginal and Torres Strait Islander partners relating to Indigenous data. IDG-PPL-012 supports the capability the community chooses.
  • Framework for Governance of Indigenous Data G2.10 supports Covers checking with the community that capability building works.
  • Framework for Governance of Indigenous Data G4.14 partial The Framework asks for community-focussed data platforms and training. IDG asks for the support the community chooses, which may include these.
PRC

Guidelines for Process

16 proposed provisional controls in domain PRC

IDG-PRC-001 Stage 6: Share & Publish provisional · v3 Audience: both Automated checks

Data sharing agreements with required clauses

Applies to: internal sensitive protected restricted CARE A1 CARE A3 CARE C3 FAIR R1.1

The clause list is compared with the BlakSmith agreement type in docs/idg/agreement-clauses.md.

Control

Indigenous data is shared only under a written agreement that the community's custodians have signed off. The agreement names the parties and the recipient, the purpose, the data in scope, the start and end dates, the formats allowed, where the data may be held, whether it may be shared onward, whether it may be used with AI, the benefit to the community, attribution, whether it is returned or destroyed at the end, breach notification, a ban on re-identification, and a review date. Clauses that are not filled in default to the most restrictive choice.

Rationale: An agreement is the community's main way to set the terms of use and to hold the recipient to them. Missing clauses are where misunderstandings and misuse start.

Maturity descriptors for IDG-PRC-001
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1A written agreement with every required clause exists before any data is shared.
IDG-ML2Agreements are signed off by the community's custodians, kept in a register, and the systems that share data check an agreement is in place.
IDG-ML3Systems enforce each clause, so data outside the scope, formats, dates or purposes of an active agreement cannot be shared.

Evidence types: agreement, register, system_check

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Data sharing agreements record parties, custodian group, required custodian sign-offs, recipient organisation and contacts, dataset scope, start and end dates, allowed formats, purposes, residency, onward sharing, a no AI training term, attribution, benefit, return or destroy, destruction attestation, a review date and secrecy references. A sharing agreement becomes active only after approved members of the named custodian group sign off; tenant owners, admins and break-glass cannot sign. The full agreement can be exported as a document with every clause.

Implementation paths: packages/core/src/governance/agreement.ts, packages/graph/src/governance-agreement.ts, packages/graph/src/sharing-agreement.ts, docs/idg/agreement-clauses.md

Automated checks: packages/graph/src/governance-agreement.test.ts, packages/graph/src/sharing-agreement.test.ts, packages/core/src/governance/governance.test.ts

Honest gaps: There is no structured breach notification clause on the agreement type yet. On legacy attached governance agreements outside the sharing-agreement workflow, purpose checks run only on protected material and above (or where a record carries its own allowed purposes or consent), an empty purpose list authorises every purpose, an omitted AI term allows AI use, and return or destroy defaults to retain under protocol.

Framework crosswalks & departures (6)
  • Protective Security Policy Framework (PSPF) 77 partial PSPF requires an agreement before sharing. IDG also requires custodian sign-off and set clauses.
  • NIST SP 800-53 Rev. 5 AC-21 partial Sharing decisions by the organisation. IDG requires a signed agreement with set clauses.
  • NIST Cybersecurity Framework (CSF) 2.0 GV.SC-05 supports
  • Information Security Manual (ISM) ISM-0072 supports
  • FAIR Guiding Principles for scientific data management and stewardship R1.1 partial The agreement sets clear terms of use, as FAIR asks of a licence, but the community sets them and they bind a named recipient only.
  • Framework for Governance of Indigenous Data G1.5 supports The Framework is about arrangements for sharing government-held data with Aboriginal and Torres Strait Islander stakeholders. IDG-PRC-001 governs any sharing of Indigenous data, and needs the community's custodians to sign off.
IDG-PRC-002 Stage 2: Collect & Consent provisional · v2 Audience: both Automated checks

Free, prior and informed consent before collection

Applies to: public internal sensitive protected restricted CARE A1 CARE E1
Control

Before Indigenous data is collected, created or brought into a system, the organisation has the free, prior and informed consent of the community, given collectively by the people with authority to give it. The community was told the purpose and the risks, could refuse without penalty, and the consent is recorded with who gave it and for what.

Rationale: Consent given after the fact, by an individual on behalf of a collective, or without the option to refuse, is not consent the community can rely on.

Maturity descriptors for IDG-PRC-002
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Consent is obtained and recorded before collection, with who gave it, for what purpose and on what date.
IDG-ML2Systems refuse to ingest data that needs collective consent unless a consent record is supplied with it.
IDG-ML3Systems check the consent record against the community's own register before ingest, and keep it with the data.

Evidence types: agreement, register, system_check

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.)

BlakSmith worked example: Connector and evidence-drop batches that write kinds needing FPIC are refused unless they carry a consent record with a holder, at least one purpose, collective consent and an acknowledged right to refuse.

Implementation paths: packages/core/src/governance/fpic.ts, packages/discovery/src/runner.ts, packages/discovery/src/evidence-ingest.ts

Automated checks: packages/core/src/governance/governance.test.ts

Honest gaps: The consent record is whatever the batch supplies. It is not checked against any stored consent and is not kept afterwards. The check does not cover records created through the API, web app or MCP, and one public register connector is exempt by name. In an evidence drop the connector name is declared by the sender, so any sender can claim that exemption.

Framework crosswalks & departures (5)
  • NIST SP 800-53 Rev. 5 PT-4 partial Individual consent, not collective free, prior and informed consent.
  • NIST SP 800-53 Rev. 5 PT-5 supports
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme APP 3 partial Collection of personal information about individuals, not collective consent.
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme APP 5 partial Notice to individuals, not collective consent.
  • Framework for Governance of Indigenous Data G3.2 supports The Framework asks agencies to partner on how data is collected. It names informed consent as a principle, but no action requires the community's collective free, prior and informed consent before collection, as IDG-PRC-002 does.
IDG-PRC-003 Stage 5: Access, Use & AI provisional · v2 Audience: both Automated checks

Purpose limitation

Applies to: sensitive protected restricted CARE A3 CARE E1
Control

Indigenous data is used only for the purposes the community agreed. Each access to sensitive material and above states its purpose, and an access for a purpose outside the agreement is refused. Running or administering the system is never a purpose that justifies reading culturally restricted material.

Rationale: Data collected for one purpose is often reused for another the community never agreed to. Purpose is the line the community drew.

Maturity descriptors for IDG-PRC-003
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Agreed purposes are written down, and staff are told not to use data for anything else.
IDG-ML2Systems require a stated purpose for access at these levels and refuse purposes outside the agreement.
IDG-ML3Stated purposes are checked against the person's role and agreement, and the community can see which purposes were used.

Evidence types: agreement, configuration, audit_log, system_check

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); relevant (Data that is relevant and empowers sustainable self-determination and effective self-governance.)

BlakSmith worked example: Material at protected level and above needs a stated purpose. A purpose outside the material's allowed purposes, its consent or its agreement is refused, and system administration and statistical reporting are refused outright on culturally bound material. The purpose is written to the audit log. For consultants and proponents, a stated purpose is also checked against their engagement.

Implementation paths: packages/core/src/classification/classification.ts, packages/core/src/classification/cultural.ts, packages/authz/src/classified.ts, packages/graph/src/access-audit.ts

Automated checks: packages/core/src/classification/classification.test.ts, packages/authz/src/classified.test.ts

Honest gaps: The purpose is declared by the person or client making the request and, apart from engagements, is not checked against their role. Sensitive material does not require a purpose. When a record has its own allowed purposes, those decide on their own and are not narrowed by the consent's purposes.

Framework crosswalks & departures (4)
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme APP 6 partial APP 6 allows some uses beyond the primary purpose without consent.
  • NIST SP 800-53 Rev. 5 PT-3 partial Purposes set by the organisation, not agreed with the community.
  • NIST SP 800-53 Rev. 5 PT-2 supports
  • ISO/IEC 38505-1: Governance of data, application of ISO/IEC 38500 to the governance of data data-use-understanding supports The governing body should understand what data is used and for what purpose. IDG-PRC-003 limits each use to the purposes the community agreed and refuses others.
IDG-PRC-004 Stage 5: Access, Use & AI provisional · v3 Audience: both Automated checks

Approval for secondary use and derived data

Applies to: internal sensitive protected restricted CARE A3 CARE C3 CARE E3 FAIR R1.1
Control

Any new use of Indigenous data, and any new dataset, model, report or other output derived from it, needs the community's approval before it is used or shared. Consent for the source data does not carry over to what is derived from it.

Rationale: Derived outputs can reveal as much as the source, and are often shared more widely. If consent carried over automatically, the community would lose control at the first derivation.

Maturity descriptors for IDG-PRC-004
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Secondary uses and derived outputs are listed and approved by the community before use.
IDG-ML2Derived records are created without consent and cannot be used until the community grants it.
IDG-ML3Derived outputs are tracked back to their sources, and the community reviews each one with any benefit it produces.

Evidence types: register, agreement, system_check

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: When records are merged or derived, the result carries no consent. Where a source's ICIP terms say derivatives need consent, the result is marked as needing its own grant and purpose checks on it fail until one is given. Derived outputs can be registered as pending with a review task for the custodian group.

Implementation paths: packages/core/src/classification/classification.ts, packages/graph/src/benefits.ts

Automated checks: packages/core/src/classification/classification.test.ts, packages/graph/src/benefits.test.ts, @blaksmith/discovery governance-verify

Honest gaps: Without that ICIP term, a derived record keeps only the overlap of its sources' allowed purposes, and if they do not overlap it has no purpose limit at all. Below protected level it has no purpose check. Nothing in the product calls the derived output registration outside tests. A reconcile write to an existing record can clear its live consent the same way, which fails closed at protected level and above but leaves lower-level material unconstrained.

Framework crosswalks & departures (4)
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme APP 6 partial APP 6 allows some secondary uses without consent. IDG requires community approval for every one.
  • NIST SP 800-53 Rev. 5 PT-3 partial No requirement that derived data needs fresh consent.
  • FAIR Guiding Principles for scientific data management and stewardship R1.1 supports FAIR asks for clear terms of reuse. IDG does not rely on a licence: each secondary use and derived dataset needs the community's approval.
  • Framework for Governance of Indigenous Data G4.8(b) supports Covers the reuse phase. IDG requires the community's approval for each new use, which is more than partnering.
IDG-PRC-005 Stage 2: Collect & Consent provisional · v1 Audience: both Automated checks

Consent variation and withdrawal

Applies to: internal sensitive protected restricted CARE A1 CARE A3
Control

A community can narrow, extend or withdraw its consent at any time. Narrowing and withdrawal take effect straight away. Broadening the purposes or extending the period is treated as a new grant that the community must give. The organisation records each change and who made it.

Rationale: Consent is an ongoing relationship, not a one-off form. A community's later decisions must carry the same weight as its first one.

Maturity descriptors for IDG-PRC-005
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Variations and withdrawals are accepted in writing and recorded.
IDG-ML2Systems apply a narrowing or withdrawal at once, and refuse to treat a broadening as anything but a new grant.
IDG-ML3The community makes variations and withdrawals directly, and can see their effect on every dataset and recipient.

Evidence types: agreement, audit_log, system_check

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.)

BlakSmith worked example: Consent is granted with purposes and an optional end date. It can be narrowed but not broadened or extended, which must be a new grant, and revoked. Revocation and expiry make the next purpose check fail closed, and each change is an audited event.

Implementation paths: packages/graph/src/consent-lifecycle.ts, packages/core/src/classification/classification.ts

Automated checks: packages/core/src/classification/classification.test.ts, @blaksmith/discovery governance-verify

Honest gaps: Consent is granted, varied and revoked by tenant owners or admins, not by the community, and who granted it is free text. Open-ended grants stay in force until revoked. Narrowing is only reachable from the verify script, not from the web app, API or MCP. Refusal of revoked consent is unit tested, but the revoke operation itself is covered only by the verify script.

Framework crosswalks & departures (1)
  • NIST SP 800-53 Rev. 5 PT-4(3) partial Individual revocation only.
IDG-PRC-006 Stage 2: Collect & Consent provisional · v1 Audience: both Automated checks

Suspension when new information comes to light

Applies to: internal sensitive protected restricted CARE E1 CARE A3
Control

When new information arises that could change the community's decision, such as newly found cultural significance, the organisation suspends use under the affected consent at once, tells the community and anyone it must notify by law, and resumes only if the community gives consent again.

Rationale: Consent given on one set of facts does not cover facts the community did not know. Carrying on while the community reconsiders can cause harm that cannot be undone.

Maturity descriptors for IDG-PRC-006
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Staff know to stop and report when they learn something that could change the community's decision.
IDG-ML2Raising new information suspends the affected consent in the system and records who raised it and what was learned.
IDG-ML3The community and any statutory recipient are notified automatically, and use resumes only on a fresh grant.

Evidence types: procedure, audit_log, system_check

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Raising new information against material records a notice, suspends its consent so the next purpose check fails closed, and audits the event with the configured notification path.

Implementation paths: packages/graph/src/consent-lifecycle.ts, packages/core/src/governance/statutory-notify.ts

Automated checks: packages/graph/src/consent-lifecycle.test.ts

Honest gaps: The notification step records a channel as dispatched but sends nothing. Only owners or admins with a recent step-up can raise new information, and it cannot be raised against material that has no consent grant. A suspension can only be lifted by a new grant.

Framework crosswalks & departures (2)
  • NIST SP 800-53 Rev. 5 no equivalent No control suspends use when new information could change a consent decision.
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme no equivalent No principle suspends use when new information comes to light.
IDG-PRC-007 Stage 5: Access, Use & AI provisional · v1 Audience: both Automated checks

Periodic access review by the custodian group

Applies to: sensitive protected restricted CARE A3 CARE R1

The yearly minimum is an operator suggestion. The community may set its own interval.

Control

The community's custodians review who has access to their data, and why, at an interval they set and at least once a year. Access the custodians do not confirm is removed.

Rationale: Access tends to outlive the reason it was given. The people with authority over the data are best placed to say whether it is still needed.

Maturity descriptors for IDG-PRC-007
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1A list of everyone with access to each community's data is given to its custodians each year.
IDG-ML2Custodians confirm or remove each person's access, and removals are carried out within an agreed time.
IDG-ML3Custodians run the review themselves in the system, and unconfirmed access is removed automatically.

Evidence types: report, meeting_record, register

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: The governance worker can publish a per-custodian-group report of granted and refused access, with unusual activity flagged, which supports a review.

Implementation paths: packages/graph/src/access-transparency.ts, packages/discovery/src/governance-worker.ts

Automated checks: @blaksmith/discovery governance-verify

Honest gaps: The report shows past access, not who currently holds access. There is no review workflow, and reports are only produced when the operator sets an export directory.

Framework crosswalks & departures (3)
  • NIST SP 800-53 Rev. 5 AC-6(7) partial Privileges are reviewed by the organisation, not by the community.
  • Information Security Manual (ISM) ISM-1647 partial Revalidation of privileged access only, by the organisation.
  • NIST Cybersecurity Framework (CSF) 2.0 PR.AA-05 partial Access is reviewed by the organisation, not the community.
IDG-PRC-008 Stage 6: Share & Publish provisional · v1 Audience: both Automated checks

Agreement review and expiry

Applies to: internal sensitive protected restricted CARE A3 CARE R1
Control

Every agreement has a review date and an end date. The organisation reviews it with the community by the review date, and when it ends, access under it stops and the return or destruction terms are carried out.

Rationale: Agreements left to run on their own outlast the people and purposes they were made for.

Maturity descriptors for IDG-PRC-008
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Each agreement has a review date and an end date in a register, and reviews are held.
IDG-ML2Reviews and expiries are raised automatically before they fall due.
IDG-ML3Expiry stops access automatically and starts the return or destruction process.

Evidence types: register, agreement, meeting_record, system_check

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: The governance worker raises an agreement review task when an agreement's review date is due.

Implementation paths: packages/core/src/governance/agreement.ts, packages/graph/src/consent-lifecycle.ts, packages/discovery/src/governance-worker.ts

Automated checks: packages/core/src/governance/governance.test.ts

Honest gaps: Agreements have no end date, so nothing expires. An agreement without a review date never raises a review. Review tasks are reminders only. The unit test covers the due-date check, not the worker creating the task.

Framework crosswalks & departures (1)
  • NIST SP 800-53 Rev. 5 PS-6 partial Review of access agreements. IDG adds an end date that stops access and starts return or destruction.
IDG-PRC-009 Stage 7: Retain, Return & Destroy provisional · v2 Audience: both Manual / Organisational

Incident and breach notification to the community

Applies to: public internal sensitive protected restricted CARE R1 CARE E1 CARE E2

Where an agreement sets no time, the operator suggests telling the community within 72 hours of becoming aware of the incident. This is a suggestion, not a legal requirement.

Control

When Indigenous data is lost, accessed without authority, disclosed or used outside the agreement, the organisation tells the affected community as soon as practicable and within the time set in the agreement. Unless the law prevents it, the community is never told later than anyone the law requires the organisation to notify. The notice says what happened, what data, what has been done and what the community can do, and the community is involved in the response.

Rationale: Legal breach schemes protect individuals. Harm to a community, such as disclosure of restricted knowledge, may not meet those thresholds at all, but the community still needs to know and to have a say in the response.

Maturity descriptors for IDG-PRC-009
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1An incident procedure names the community contact for each dataset and the time for notifying them.
IDG-ML2Every incident affecting Indigenous data is recorded with when the community was told, and the procedure is tested.
IDG-ML3Detection feeds the community notification directly, and the community takes part in the review of each incident.

Evidence types: procedure, register, report, agreement

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (7)
  • Information Security Manual (ISM) ISM-1880 partial Reporting to customers. IDG requires telling the community and involving it in the response.
  • Information Security Manual (ISM) ISM-0133 partial Advising data owners of a spill. The community may not be the data owner.
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme NDB partial The scheme covers serious harm to individuals, not harm to a community.
  • NIST SP 800-53 Rev. 5 IR-6 partial Reporting to organisation-defined authorities, not the community.
  • NIST Cybersecurity Framework (CSF) 2.0 RS.CO-02 partial Stakeholders are chosen by the organisation.
  • Protective Security Policy Framework (PSPF) 26 supports
  • Information Security Manual (ISM) ISM-0142 supports Reports a key compromise to the chief information security officer. If it may expose the data the key protects, IDG requires telling the community.
IDG-PRC-010 Stage 7: Retain, Return & Destroy provisional · v3 Audience: both Automated checks

Destruction and attestation of destruction

Applies to: internal sensitive protected restricted CARE A1 CARE R1
Control

When an agreement ends or the community asks for destruction, the organisation destroys the data, including copies in backups, derived data and copies held by recipients. A named accountable person signs an attestation that lists what was destroyed, where, how and when, and the community receives it.

Rationale: Data that is meant to be gone often survives in backups, exports and derived files. A signed attestation makes someone accountable for finding every copy.

Maturity descriptors for IDG-PRC-010
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1A destruction procedure covers primary copies, backups, derived data and recipients' copies.
IDG-ML2Each destruction is attested by a named accountable person and the attestation is given to the community.
IDG-ML3Encryption keys for the data are destroyed as part of the process, and the attestation is recorded in a tamper-evident log the community can check.

Evidence types: procedure, attestation, audit_log

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Agreements record whether data is returned, destroyed or retained under protocol. Destroying a custodian group's encryption key with the erasure script makes the encrypted properties of that group's records unreadable, including in encrypted backups.

Implementation paths: packages/core/src/governance/agreement.ts, infra/aws/scripts/erase-custodian-key.sh, docs/data-retention.md

Automated checks: packages/crypto/src/crypto.test.ts

Honest gaps: The return or destroy term is never acted on. There is no attestation record. Destroying a key leaves record names, graph structure, embedding text and derived records held under other keys readable, and nothing is encrypted when no key provider is configured. Key erasure is a manual script whose record is not written to the audit log. Plaintext that comes back in a restored backup is only handled by a manual runbook, and exports already taken are out of reach.

Framework crosswalks & departures (10)
  • Protective Security Policy Framework (PSPF) 73 partial Secure disposal. IDG adds backups, derived data, recipients and a signed attestation.
  • NIST SP 800-53 Rev. 5 MP-6 partial Sanitising media only.
  • NIST SP 800-53 Rev. 5 SI-12(3) partial Disposal after retention. IDG adds destruction on community request and an attestation.
  • Information Security Manual (ISM) ISM-0313 supports
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme APP 11 partial Destroy or de-identify when no longer needed. IDG adds an attestation to the community.
  • Information Security Manual (ISM) ISM-0348 supports
  • Information Security Manual (ISM) ISM-0363 supports
  • Information Security Manual (ISM) ISM-1735 supports
  • Information Security Manual (ISM) ISM-2053 supports Asks software suppliers for end of life procedures that cover destroying data. IDG requires destruction whenever an agreement ends or the community asks, not only at a product's end of life.
  • TRUST Principles for digital repositories no equivalent TRUST asks repositories to preserve data for the long term. IDG requires data to be destroyed when the community asks or the agreement ends, and the destruction attested.
IDG-PRC-011 Stage 6: Share & Publish provisional · v2 Audience: both Manual / Organisational

Onward sharing is controlled by the sharing organisation

Applies to: internal sensitive protected restricted CARE A3 CARE R1
Control

The organisation sharing Indigenous data writes a ban on onward sharing into every agreement, allows an exception only where the community approves a named onward recipient, records each approval, and makes sure the onward recipient is bound by the same terms. The recipient's own obligation is IDG-CON-005.

Rationale: Each onward share moves the data further from the community's sight and control.

Maturity descriptors for IDG-PRC-011
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Every agreement bans onward sharing unless the community approves it.
IDG-ML2Each approved onward share is recorded with the community's approval and the terms that bind the onward recipient.
IDG-ML3Exports are traceable to the recipient, so an unapproved onward copy can be identified.

Evidence types: agreement, register, attestation

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (3)
  • NIST SP 800-53 Rev. 5 AC-21 partial Sharing decisions by the organisation, not approval by the community.
  • Protective Security Policy Framework (PSPF) 77 supports
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme APP 6 supports
IDG-PRC-012 Stage 6: Share & Publish provisional · v3 Audience: both Manual / Organisational

Re-identification risk is controlled before release

Applies to: internal sensitive protected restricted CARE E1 CARE E2
Control

The organisation sharing Indigenous data writes a ban on re-identification and unapproved linkage into every agreement, releases data at the least detail the purpose needs, and records any linkage the community has approved. The recipient's own obligation is IDG-CON-006.

Rationale: Removing names does not stop small populations from being identified. Linkage with other data is one of the most common ways that happens.

Maturity descriptors for IDG-PRC-012
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Every agreement bans re-identification and unapproved linkage.
IDG-ML2Data is released at the least detail the purpose needs, and approved linkages are recorded with the community's approval.
IDG-ML3Each release is assessed for re-identification risk before it leaves the organisation.

Evidence types: agreement, attestation, procedure

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (3)
  • NIST SP 800-53 Rev. 5 SI-19 partial De-identification techniques. IDG adds a ban on re-identification and linkage in every agreement.
  • NIST SP 800-53 Rev. 5 SI-19(8) supports
  • Framework for Governance of Indigenous Data G4.12 supports The Framework asks agencies to explore ways to promote collective or group privacy. IDG-PRC-012 sets a concrete rule for shared data: no re-identification or unapproved linkage, and the least detail the purpose needs.
IDG-PRC-013 Stage 7: Retain, Return & Destroy provisional · v3 Audience: community Automated checks

Return of data to the community

Applies to: public internal sensitive protected restricted CARE A2 CARE C3
Control

The community can ask for its data back at any time, and receive it in a usable form with its classification, cultural protocols and agreements attached, so it can keep governing the data itself.

Rationale: Returning data is part of returning control. Data handed back without its protocols, or in a form the community cannot use, does not do that.

Maturity descriptors for IDG-PRC-013
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Data is returned on request, in a format agreed with the community.
IDG-ML2Returned data carries its classification, protocols and agreements, and the return is recorded.
IDG-ML3The community can retrieve its data itself at any time, in open formats, with its protocols intact.

Evidence types: procedure, audit_log, report

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); contextual (Data that is contextual and disaggregated (available and accessible at individual, community and First Nations levels).)

BlakSmith worked example: A repatriation package exports readable records with their classification, protocols and agreements, refuses a heritage export that would strip protocols, refuses consultants and proponents, and writes an audit event.

Implementation paths: packages/graph/src/repatriation.ts, packages/core/src/governance/export-package.ts

Automated checks: packages/graph/src/repatriation.test.ts

Honest gaps: The package is a JSON download that any user who can read the records can produce, not a return under the community's control. There is no community self-service.

Framework crosswalks & departures (6)
  • Information Security Manual (ISM) ISM-1574 partial Portability between service providers. IDG requires return to the community with protocols attached.
  • NIST Cybersecurity Framework (CSF) 2.0 GV.SC-10 supports
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme APP 12 partial Access for an individual, not return to a community.
  • TRUST Principles for digital repositories sustainability supports TRUST keeps data available by having the repository preserve it. IDG makes sure the community can take its data back and keep it in its own care, whatever happens to the operator.
  • Framework for Governance of Indigenous Data G3.3 partial The Framework's process for people to request access to government-held data covers part of this control. IDG adds that the community can ask for its data back at any time and receives it in a usable form with its classification, cultural protocols and agreements attached. The Framework also asks for reasons for any refusal, response times and a right of review, which IDG-PRC-013 does not set.
  • Framework for Governance of Indigenous Data G4.14 supports The Framework asks for community-focussed platforms and training so communities can use and maintain their own data. IDG-PRC-013 only returns the data in a usable form.
IDG-PRC-014 Stage 1: Plan & Govern provisional · v1 Audience: both Manual / Organisational

Community data priorities

Applies to: public internal sensitive protected restricted CARE A2 CARE C1
Control

The organisation asks each community it holds data about what data the community wants collected, kept, analysed or made available to it, and for what purposes. It records those priorities, acts on them where it can, and tells the community what it has done, and why where it has not.

Rationale: Data that answers the organisation's questions but not the community's does little for self-determination. Asking the community what it needs is where relevant data starts.

Maturity descriptors for IDG-PRC-014
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The organisation has asked each community it holds data about for its data priorities, and recorded them.
IDG-ML2Priorities are reviewed with the community at an interval it agrees, and the organisation reports what it has done on each.
IDG-ML3Community priorities shape what the organisation collects and analyses, and the community can point to decisions they changed.

Evidence types: register, meeting_record, report

Maiam nayri Wingara: relevant (Data that is relevant and empowers sustainable self-determination and effective self-governance.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (2)
  • Framework for Governance of Indigenous Data G4.9 partial The Framework's ask that agencies learn what additional or alternative data people want collected covers part of this control. IDG adds recording those priorities, acting on them where it can and telling the community what was done, and why where it was not. The Framework also asks for training community members to collect the data, which IDG does not require.
  • Framework for Governance of Indigenous Data G1 supports Covers making sure the community's priorities are reflected in data about it.
IDG-PRC-015 Stage 5: Access, Use & AI provisional · v1 Audience: both Manual / Organisational

Disaggregated data for the community on request

Applies to: public internal sensitive protected restricted CARE A2 CARE C2
Control

When a community asks, the organisation gives it data about that community at the level of detail it asks for, such as for the community as a whole or for a Nation, language group or place the community names. The data goes through the people the community has authorised (IDG-GOV-001), with its cultural protocols still applied (IDG-TEC-002, IDG-GOV-002), so more detail does not lift a protocol on protocol-bound material within the community. Each person can get data about themselves, also with the community's cultural protocols applied. Data about other individuals is released only where the law and those people's own rights allow. If the organisation cannot meet a request, it says why and offers what it can.

Rationale: Data published only in aggregate hides differences between communities and is easily read as deficit. Communities need data at the level they choose in order to govern themselves. Giving more detail to the community is not the same as releasing it to others, so the protections in IDG-PRC-012 still apply to everyone outside the community's authority.

Maturity descriptors for IDG-PRC-015
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The organisation can tell a community at what levels of detail it holds data about that community.
IDG-ML2Requests for disaggregated data are answered within a time agreed with the community, with reasons and alternatives for anything refused.
IDG-ML3The community can get data about itself at the levels it chooses without a separate request each time, under its own access rules.

Evidence types: procedure, register, report

Maiam nayri Wingara: contextual (Data that is contextual and disaggregated (available and accessible at individual, community and First Nations levels).)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (2)
  • Framework for Governance of Indigenous Data G4.11 exceeds The Framework asks agencies to explore releasing disaggregated data when partners ask, where legally and ethically acceptable. IDG requires an answer, with reasons and alternatives for anything refused.
  • Framework for Governance of Indigenous Data G3.3 supports Covers giving reasons and alternatives when a request is refused.
IDG-PRC-016 Stage 2: Collect & Consent provisional · v1 Audience: both Manual / Organisational

Data stewardship and data quality reviewed with the community

Applies to: public internal sensitive protected restricted CARE E1 CARE E3 CARE A3 FAIR R1.2
Control

Each set of Indigenous data the organisation holds has a named data steward (IDG-PPL-001), who keeps a record of where the data came from, how it was collected and what it can and cannot support. The community can review the data about it, have errors corrected and have its own context recorded with the data.

Rationale: Inaccurate or decontextualised data about Aboriginal and Torres Strait Islander people has long been used to tell deficit stories. Quality judged only by the organisation repeats that. The community knows things about the data that the organisation does not.

Maturity descriptors for IDG-PRC-016
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Each set of Indigenous data has a named steward and a record of its source, how it was collected and its known limitations.
IDG-ML2The community can ask for errors to be corrected and context to be added. The organisation acts on each request and records what it did.
IDG-ML3Data quality is reviewed with the community at an interval it agrees, and the community's view of the data's quality is recorded with the data.

Evidence types: register, procedure, report

Maiam nayri Wingara: contextual (Data that is contextual and disaggregated (available and accessible at individual, community and First Nations levels).); accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (2)
  • Framework for Governance of Indigenous Data G4.8 partial The Framework's ask to improve the quality of Indigenous data, including BADDR data, in partnership covers part of this control. IDG adds a named steward, a record of where the data came from and what it can and cannot support, and correction and context from the community. The Framework also asks for better identification of Aboriginal and Torres Strait Islander people in mainstream data collection (its item a), which IDG does not require.
  • FAIR Guiding Principles for scientific data management and stewardship R1.2 supports The steward's record of source and collection method is part of the data's provenance.
TEC

Guidelines for Technology

17 proposed provisional controls in domain TEC

IDG-TEC-001 Stage 3: Classify & Label provisional · v3 Audience: both Automated checks

Every record carries a classification that can only be raised automatically

Applies to: public internal sensitive protected restricted CARE A3 CARE E1 FAIR R1
Control

Every record of Indigenous data carries a sensitivity classification from an ordered scale. When records are combined or reconciled, the result takes the strictest classification of its sources. Automated processes may raise a classification but never lower it; lowering needs a deliberate, authorised and recorded decision.

Rationale: Access, encryption and export decisions all depend on the classification. If a sync job or a merge can quietly lower it, every other control is undone.

Maturity descriptors for IDG-TEC-001
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1A classification scheme exists and is applied to Indigenous data, with a recorded default.
IDG-ML2Systems store a classification on every record and take the strictest level when records are combined.
IDG-ML3Automated lowering is impossible, every change is recorded with who made it, and history reads at the current level.

Evidence types: configuration, system_check, audit_log

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Every node, edge and document carries a classification from a five-level ladder. Merging takes the strictest level and protocols. Reconciliation can raise but never lower a classification; only an explicit change by a human owner or admin with step-up can. Node history and as-of reads are shown at least as strict as the node's current level.

Implementation paths: packages/core/src/classification/levels.ts, packages/core/src/classification/classification.ts, packages/authz/src/classified.ts, docs/data-classification.md

Automated checks: packages/core/src/classification/classification.test.ts, @blaksmith/graph classification-verify

Honest gaps: The default level is internal, so data imported without a classification is not treated as sensitive. Edge history and as-of edge reads use the edge's historical classification, so a raised edge can still be read at its earlier level.

Framework crosswalks & departures (5)
  • Protective Security Policy Framework (PSPF) 59 partial The originator assesses sensitivity. IDG adds that automated processes may only raise a classification.
  • Protective Security Policy Framework (PSPF) 60 partial PSPF sets classification at the lowest reasonable level. IDG adds that only a deliberate decision may lower it.
  • NIST SP 800-53 Rev. 5 AC-16 partial Security attributes in general. IDG adds the raise-only rule.
  • FAIR Guiding Principles for scientific data management and stewardship R1 supports Every record carries an accurate sensitivity classification, one of the attributes reuse depends on.
  • Information Security Manual (ISM) ISM-0393 partial The ISM classifies databases and their contents by the data they hold, which covers part of this control. IDG adds that every record carries its own classification, that combined records take the strictest level, and that automated processes can only raise a classification. IDG-TEC-001 does not require the database itself to be classified, as the ISM does.
IDG-TEC-002 Stage 3: Classify & Label provisional · v3 Audience: both Automated checks

Cultural protocols and Local Contexts labels travel with the data

Applies to: public internal sensitive protected restricted CARE A3 CARE R3 FAIR R1.1 FAIR R1.3

TK (Traditional Knowledge) and BC (Biocultural) Labels are published by Local Contexts, checked at localcontexts.org on 1 November 2026.

Control

Cultural protocols and Local Contexts Traditional Knowledge (TK) and Biocultural (BC) labels are stored with each record they apply to, enforced by the system where they restrict access or use, and carried with the record into every copy, export and derived record.

Rationale: A protocol that lives in a separate document is lost the first time the data is copied. Labels only protect anything if systems act on them.

Maturity descriptors for IDG-TEC-002
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Protocols and labels are recorded against the records they apply to.
IDG-ML2Protocols that restrict access or use are enforced by the system, and labels are included in every export.
IDG-ML3Every label's meaning is enforced, labels are kept in sync with the community's own Local Contexts records, and derived records inherit them.

Evidence types: configuration, system_check

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); contextual (Data that is contextual and disaggregated (available and accessible at individual, community and First Nations levels).)

BlakSmith worked example: Records carry cultural protocols, each with a minimum level, custodian requirement and presentation flags, plus Local Contexts TK labels. Merged records keep the union of protocols. Seasonal labels restrict access to community-supplied windows. The Non-Commercial label refuses commercial use wherever a purpose check runs. TK labels can be resynced from the Local Contexts Hub.

Implementation paths: packages/core/src/classification/cultural.ts, packages/core/src/classification/tk-labels.ts, packages/core/src/classification/classification.ts, packages/discovery/src/local-contexts.ts

Automated checks: packages/core/src/classification/classification.test.ts, @blaksmith/graph classification-verify, @blaksmith/discovery governance-verify

Honest gaps: BC labels are not supported. Only the Seasonal and Non-Commercial labels are enforced, and Non-Commercial is not checked on internal or sensitive records that have no purpose limit, consent or other constraint. Labels such as secret or sacred, men restricted, women restricted and community use only restrict nothing unless a matching cultural protocol is also set. Gender-restricted protocols are enforced through custodian group membership, not by checking gender.

Framework crosswalks & departures (6)
  • NIST SP 800-53 Rev. 5 AC-16 partial Attributes chosen by the organisation. IDG requires cultural protocols and labels set by the community.
  • NIST SP 800-53 Rev. 5 AC-16(5) supports
  • FAIR Guiding Principles for scientific data management and stewardship R1.1 partial FAIR asks for a clear usage licence. IDG carries the community's protocols and labels with the data and enforces them, which a licence alone does not do.
  • FAIR Guiding Principles for scientific data management and stewardship R1.3 partial Local Contexts labels are a community standard for Indigenous data. IDG enforces them as well as recording them.
  • TRUST Principles for digital repositories user-focus partial TRUST asks repositories to meet the norms of their user communities. IDG carries and enforces the norms of the community the data is about, through its protocols and labels, whether or not that community uses the system.
  • Framework for Governance of Indigenous Data G3.5(a) supports The Framework asks for metadata flags to make data findable and align it with FAIR and CARE. IDG's labels carry the community's protocols and are enforced. They are not for findability.
IDG-TEC-003 Stage 3: Classify & Label provisional · v2 Audience: both Automated checks

Existence of restricted records fails closed

Applies to: protected restricted Protocol-bound only CARE E1 CARE A3 FAIR: CARE precedence
Control

Where a community's protocol requires it, a person without authority cannot learn that a restricted record exists: it does not appear in search, lists, counts, maps, graphs or error messages. When the system cannot tell whether someone may know, it hides the record.

Rationale: For some knowledge, revealing that a record exists, or where it is, is itself the harm.

Maturity descriptors for IDG-TEC-003
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Restricted records are left out of the main search and listing screens for people without authority.
IDG-ML2Every read path, including search, counts, maps, exports and error messages, hides the record's existence.
IDG-ML3Hiding is tested automatically across every read path on each change.

Evidence types: configuration, system_check

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Protocols can hide a record's existence from anyone without custody, and the check fails closed when authority is not established. In the web app a refused read of a hidden record looks the same as a missing one, and proponents without custody are not shown hidden material.

Implementation paths: packages/core/src/classification/existence.ts, packages/authz/src/classified.ts, packages/graph/src/classified-read.ts

Automated checks: packages/core/src/classification/existence.test.ts, packages/authz/src/classified.test.ts

Honest gaps: The REST API and MCP word the not-found error differently for a missing record, which includes its ID, and a hidden one, which does not, so a caller can tell that a hidden record exists. No single test covers every read path, such as search, counts and maps.

Framework crosswalks & departures (4)
  • NIST SP 800-53 Rev. 5 AC-3 supports IDG also hides that a record exists.
  • TRUST Principles for digital repositories responsibility supports TRUST asks repositories to protect sensitive information. Hiding that a restricted record exists is one way IDG does this.
  • Information Security Manual (ISM) no equivalent No control requires hiding the existence of a record.
  • FAIR Guiding Principles for scientific data management and stewardship no equivalent No FAIR principle requires hiding that a record exists. FAIR allows access control on metadata (A1.2) and does not require a public index (F4), so a FAIR repository can hide restricted records, but IDG requires it where a community protocol asks.
IDG-TEC-004 Stage 4: Store & Protect provisional · v3 Audience: both Automated checks

Encryption at rest for sensitive Indigenous data

Applies to: sensitive protected restricted CARE E1
Control

Sensitive Indigenous data is encrypted at rest at the application level, in addition to any storage encryption, with a fresh data key for each item and authenticated encryption. Plaintext does not appear in database columns, version history or backups.

Rationale: Storage encryption protects against a stolen disk, not against anyone with database access. Application-level encryption keeps the data unreadable to people who can read the database.

Maturity descriptors for IDG-TEC-004
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Storage holding Indigenous data is encrypted at rest.
IDG-ML2Sensitive fields are encrypted by the application before they are stored, including in history and backups.
IDG-ML3All content, including names and derived search data, is encrypted, and a scheduled check proves no plaintext is stored.

Evidence types: configuration, system_check

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Record properties at sensitive level and above are sealed with AES-256-GCM envelope encryption, a fresh data key and IV per payload, and the encryption context as additional authenticated data, before they are written to rows or version snapshots. The verify script checks the secret is absent from the database column and from every snapshot.

Implementation paths: packages/crypto/src/envelope.ts, packages/crypto/src/fields.ts, packages/crypto/src/resolve.ts

Automated checks: packages/crypto/src/crypto.test.ts, @blaksmith/graph encryption-verify

Honest gaps: Only property values are sealed. Record names, kinds, graph structure and embedding text are stored in plaintext, as are property names and the classification itself. Unless NODE_ENV is production, a deployment with no key provider configured stores properties in plaintext. The server decrypts in memory, so this is not end to end encryption.

Framework crosswalks & departures (8)
  • Information Security Manual (ISM) ISM-1080 partial Approved algorithms only. IDG adds application-level encryption and no plaintext in history or backups.
  • NIST SP 800-53 Rev. 5 SC-28 partial Storage encryption can satisfy SC-28. IDG adds application-level encryption with a fresh key per item.
  • NIST SP 800-53 Rev. 5 SC-28(1) partial IDG adds application-level encryption with a fresh key per item.
  • NIST Cybersecurity Framework (CSF) 2.0 PR.DS-01 partial An outcome statement. IDG sets the mechanism.
  • TRUST Principles for digital repositories responsibility supports Authenticated encryption detects changes to stored data.
  • TRUST Principles for digital repositories technology supports Encryption at rest is part of a secure service.
  • Information Security Manual (ISM) ISM-1059 partial Encrypts all data on media with ASD-approved cryptography. IDG adds application-level encryption with a fresh data key for each item.
  • Information Security Manual (ISM) ISM-1811 supports Keeps backups secure. IDG also keeps plaintext out of backups.
IDG-TEC-005 Stage 4: Store & Protect provisional · v3 Audience: both Automated checks

Encryption in transit

Applies to: public internal sensitive protected restricted CARE E1
Control

Indigenous data is encrypted whenever it crosses a network, using current TLS, with certificates verified, and unencrypted connections refused or redirected.

Rationale: Data crossing a network unencrypted can be read or altered by anyone on the path.

Maturity descriptors for IDG-TEC-005
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Public endpoints use TLS and redirect plain HTTP.
IDG-ML2Connections to databases, storage and between services are encrypted, and secure cookies are required.
IDG-ML3Every connection, including inside private networks, uses TLS with certificate verification, and weak protocols are refused.

Evidence types: configuration, system_check

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: The Terraform load balancer serves TLS 1.2 or 1.3, the CDK one TLS 1.3, and both redirect HTTP. The database forces TLS and the application connects with TLS required. Storage buckets refuse non-TLS requests. In production, authentication requires HTTPS origins and secure cookies.

Implementation paths: infra/aws/terraform/app.tf, infra/aws/terraform/data.tf, packages/db/src/environment.ts, packages/auth/src/auth.ts

Automated checks: packages/auth/src/auth.test.ts

Honest gaps: Traffic from the load balancer to the application, and between the web app and the API, is plain HTTP inside the private network. The database connection encrypts but does not verify the server certificate. There are no site-wide HSTS or content security policy headers.

Framework crosswalks & departures (7)
  • Information Security Manual (ISM) ISM-1139 partial Latest TLS only. IDG adds certificate verification and refusing plain connections.
  • NIST SP 800-53 Rev. 5 SC-8 partial Confidentiality or integrity, by any mechanism. IDG requires both, with TLS.
  • NIST SP 800-53 Rev. 5 SC-8(1) partial IDG adds certificate verification and refusing plain connections.
  • NIST Cybersecurity Framework (CSF) 2.0 PR.DS-02 partial An outcome statement. IDG sets the mechanism.
  • TRUST Principles for digital repositories technology supports Encryption in transit is part of a secure service.
  • Information Security Manual (ISM) ISM-1781 partial Encrypts all network traffic with ASD-approved cryptography. IDG adds certificate verification.
  • Information Security Manual (ISM) ISM-1277 supports
IDG-TEC-006 Stage 4: Store & Protect provisional · v2 Audience: both Automated checks

Key custody options up to community-held keys

Applies to: sensitive protected restricted CARE A1 CARE A3
Control

The keys that protect a community's data can be held by the operator, by the customer organisation, or by the community itself, as the community chooses. Keys for different custodian groups are separate, and a community's key is never placed in operator escrow.

Rationale: Whoever holds the key decides whether the data can be read. A community that holds its own key can withdraw access without asking anyone.

Maturity descriptors for IDG-TEC-006
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Keys for Indigenous data are managed in a key management service, separate from the data.
IDG-ML2Each custodian group has its own key, and community keys are never escrowed by the operator.
IDG-ML3A community can hold its own key in its own account, and every use of it is visible to the community.

Evidence types: configuration, register, audit_log

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.)

BlakSmith worked example: Each tenant chooses vendor, customer, customer with escrow, or external key custody. Custodian groups can have their own keys, which are looked up before the tenant key and are never stored with vendor escrow. A documented option lets a community hold its own key in its own AWS account.

Implementation paths: packages/crypto/src/key-custody.ts, packages/crypto/src/community-keys.ts, docs/key-custody.md, infra/aws/community-key/README.md

Automated checks: packages/crypto/src/key-custody.test.ts

Honest gaps: The tenant, not the community, sets the custody mode. Records with joint custodians are sealed under the first group's key only. A community key registration is an ordinary record kind that anyone who can create records can write, and registrations are not separated by tenant, so a registration could point a custodian group at an unintended key. The registration service itself has no caller in the product. No live cross-account or recovery drill has been run, and community-side key policy changes do not reach the operator's alerts.

Framework crosswalks & departures (4)
  • NIST SP 800-53 Rev. 5 SA-9(6) partial Organisation-controlled keys, not community-held keys.
  • NIST SP 800-53 Rev. 5 SC-12 supports
  • Information Security Manual (ISM) ISM-0507 supports
  • TRUST Principles for digital repositories technology supports Key management is part of a secure service. IDG also lets the community hold the keys.
IDG-TEC-007 Stage 7: Retain, Return & Destroy provisional · v3 Audience: both Automated checks

Cryptographic erasure per custodian group

Applies to: sensitive protected restricted CARE A1 CARE E3
Control

A community can have its data made permanently unreadable by destroying the key that protects it, without affecting any other community's data. The erasure is authorised, recorded and reported to the community.

Rationale: Deleting every copy of data, including backups, is hard to prove. Destroying the only key makes every encrypted copy unreadable at once.

Maturity descriptors for IDG-TEC-007
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1A documented procedure can destroy a custodian group's key on the community's request.
IDG-ML2Erasure affects only that group's data, needs a recorded reference and reason, and is logged.
IDG-ML3Erasure is tested in a live drill, recorded in the tamper-evident audit log, and confirmed to the community.

Evidence types: procedure, audit_log, system_check

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Each custodian group's payloads are sealed under that group's key. A unit test shows, within one local provider instance, that blocking one group's key leaves other groups readable. The erasure script schedules deletion of the group's KMS key after a reference, justification and typed confirmation.

Implementation paths: packages/crypto/src/fields.ts, infra/aws/scripts/erase-custodian-key.sh, docs/key-custody.md

Automated checks: packages/crypto/src/crypto.test.ts

Honest gaps: The local provider test does not prove permanent erasure: a fresh provider instance can decrypt again. Statutory overlay material for a group is sealed under a separate key the script does not destroy, records sealed under another joint custodian's key survive, and under customer custody without a group key material falls back to the tenant key, so per-group erasure is not possible. Erasure leaves names, graph structure and embedding text readable. There is no in-app erasure path, the script's record is printed rather than written to the audit log, and no live erasure drill has been run.

Framework crosswalks & departures (4)
  • NIST SP 800-53 Rev. 5 MP-6 supports
  • NIST SP 800-53 Rev. 5 SC-12 supports
  • TRUST Principles for digital repositories no equivalent TRUST asks repositories to preserve data for the long term. IDG lets a community make its data unreadable for good by destroying its key.
  • Information Security Manual (ISM) no equivalent No ISM control lets a community make its data unreadable by destroying its key. Two ISM controls pull the other way. ISM-0455 asks, where practical, for a way to recover data when a key is unavailable; IDG makes a community's data unrecoverable when its key is destroyed, and never places a community's key in escrow (IDG-TEC-006). ISM-2151 asks for backups that cannot be deleted during their retention period; destroying the key is how IDG makes copies in such backups unreadable.
IDG-TEC-008 Stage 5: Access, Use & AI provisional · v2 Audience: both Automated checks

Access control that operator roles cannot override

Applies to: sensitive protected restricted Protocol-bound only CARE A3 FAIR A1.2
Control

The system enforces, in code that every read path uses, that protocol-bound data can only be read by people the community has authorised. No administrator role, platform account, service account, AI agent or emergency access mechanism can bypass that check.

Rationale: A rule that an administrator can switch off protects nothing against the administrator. This is the technical side of IDG-GOV-002.

Maturity descriptors for IDG-TEC-008
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Access to protocol-bound data is limited by configuration to authorised people.
IDG-ML2A single enforcement point checks custodian authority on every read, and refuses administrators, service accounts and AI agents without it.
IDG-ML3The refusal is tested automatically on every change, including for emergency access and every API surface.

Evidence types: configuration, system_check, audit_log

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: One decision function checks custodian authority before clearance on every classified read. For protocols that require custodian authority, it refuses the tenant owner, API keys and AI agents without custody, and break-glass cannot help. The refusal is unit tested and exercised by the verify scripts.

Implementation paths: packages/authz/src/classified.ts, packages/graph/src/classified-read.ts

Automated checks: packages/authz/src/classified.test.ts, @blaksmith/graph classification-verify, @blaksmith/discovery governance-verify

Honest gaps: The deceased person protocol does not require custodian authority, so those records are gated by clearance, which break-glass can override. An empty custodian group's first members are bootstrapped by two owners or admins (never adding an owner or admin) and remain provisional pending community confirmation (issue #286). The database owner connection is not subject to these checks.

Framework crosswalks & departures (6)
  • NIST SP 800-53 Rev. 5 AC-3 partial Access enforcement in general. IDG adds that no administrator, service account or emergency access can bypass it.
  • NIST SP 800-53 Rev. 5 AC-3(10) exceeds IDG allows no override for protocol-bound data.
  • NIST Cybersecurity Framework (CSF) 2.0 PR.AA-05 supports
  • Information Security Manual (ISM) ISM-1268 supports
  • FAIR Guiding Principles for scientific data management and stewardship A1.2 exceeds FAIR allows authentication and authorisation where necessary. IDG requires a check, set by the community, that no operator role can bypass.
  • TRUST Principles for digital repositories responsibility supports TRUST asks repositories to protect sensitive information and keep the system secure. IDG also stops operator roles from overriding the community's access decisions.
IDG-TEC-009 Stage 4: Store & Protect provisional · v2 Audience: both Automated checks

Tenant isolation enforced by the database

Applies to: public internal sensitive protected restricted CARE E1 CARE A3 FAIR A1.2
Control

Where one system holds data for more than one organisation or community, the database itself refuses to return or change another tenant's data, even if application code has a bug, and fails closed when no tenant is set.

Rationale: Application checks can be forgotten in one query. A database-level rule catches the query that was missed.

Maturity descriptors for IDG-TEC-009
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Tenant data is separated by application checks on every query.
IDG-ML2Database row-level security restricts every tenant table, and the application connects with a role that is subject to it.
IDG-ML3Isolation is verified automatically against a live database on every change, and no routine process runs with a role that bypasses it.

Evidence types: configuration, system_check

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Row-level security policies scope every tenant table to the current tenant. The application role sees nothing when no tenant is set, cannot write across tenants, and cannot read session data. Live verify scripts check this against Postgres.

Implementation paths: docs/security-rls.md, packages/db/src/tenant-scope.ts, packages/db/src/data-plane.ts

Automated checks: @blaksmith/graph rls-verify, @blaksmith/graph rls-enforcement-verify

Honest gaps: Policies are not forced on the table owner, and authentication, the worker's tenant listing and retention use the owner connection. Unless NODE_ENV is production, an unset application database URL silently falls back to the owner connection, so row-level security is not enforced.

Framework crosswalks & departures (6)
  • NIST SP 800-53 Rev. 5 AC-3 supports
  • NIST SP 800-53 Rev. 5 SC-4 supports
  • Information Security Manual (ISM) ISM-1268 supports
  • FAIR Guiding Principles for scientific data management and stewardship A1.2 supports Tenant isolation is part of the authorisation that keeps one community's data from another.
  • TRUST Principles for digital repositories responsibility supports Database-enforced tenant isolation protects each community's sensitive information.
  • TRUST Principles for digital repositories technology supports Database-enforced tenant isolation is part of a secure service.
IDG-TEC-010 Stage 8: Measure & Assure provisional · v3 Audience: both Automated checks

Tamper-evident audit log

Applies to: sensitive protected restricted CARE R1 CARE A2 FAIR R1.2
Control

Every access to and change of Indigenous data, including refused attempts, is written to an append-only log in which any alteration, deletion or reordering can be detected. The log is kept for at least as long as the data and its agreements.

Rationale: An audit log that an insider can edit cannot settle a dispute about what happened.

Maturity descriptors for IDG-TEC-010
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Access and changes are logged and the log is protected from routine editing.
IDG-ML2The log is hash-chained so changes are detectable, and the application cannot update or delete entries.
IDG-ML3The chain is verified on a schedule and its head is anchored outside the operator's control.

Evidence types: audit_log, configuration, system_check

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Events are chained by SHA-256 over the previous hash and the canonical event. Unique database constraints refuse duplicate predecessors, duplicate sequence numbers and a second genesis event per tenant, and the application role cannot update or delete events or version snapshots. The verify script detects modification, deletion and truncation.

Implementation paths: packages/graph/src/audit-chain.ts, packages/db/drizzle/0007_audit_hash_chain.sql

Automated checks: @blaksmith/graph audit-chain-verify

Honest gaps: The database owner role can still rewrite the chain. The hash column is nullable and verification counts an event without a hash as unchained rather than failing. The chain is not verified on a schedule.

Framework crosswalks & departures (13)
  • NIST SP 800-53 Rev. 5 AU-9 partial Protects audit information. IDG adds logging every access, including refusals, in a chain that shows tampering.
  • NIST SP 800-53 Rev. 5 AU-12 supports
  • NIST SP 800-53 Rev. 5 AU-11 partial Retention for an organisation-defined period. IDG keeps logs as long as the data and its agreements.
  • NIST SP 800-53 Rev. 5 AU-10 supports
  • Information Security Manual (ISM) ISM-1815 partial Protection from modification and deletion. IDG adds detection of reordering and logging of refusals.
  • Information Security Manual (ISM) ISM-1988 partial At least 12 months. IDG keeps logs as long as the data and its agreements.
  • NIST Cybersecurity Framework (CSF) 2.0 PR.PS-04 supports
  • FAIR Guiding Principles for scientific data management and stewardship R1.2 supports The log records every change to the data, which is part of its provenance.
  • TRUST Principles for digital repositories responsibility supports The log records every change to holdings, and any alteration of that record can be detected.
  • Information Security Manual (ISM) ISM-1405 supports
  • Information Security Manual (ISM) ISM-1985 supports Protects event logs from unauthorised access. IDG also gives the community the record for its own data (IDG-PPL-010).
  • Information Security Manual (ISM) ISM-0988 supports
  • Information Security Manual (ISM) ISM-1989 partial Retention set by the National Archives of Australia's AFDA Express. IDG keeps logs at least as long as the data and its agreements.
IDG-TEC-011 Stage 8: Measure & Assure provisional · v2 Audience: community Automated checks

Communities can verify the audit record independently

Applies to: sensitive protected restricted CARE A2 CARE R1
Control

A community can receive the audit record for its data, and a digest anchored outside the operator's control, and check for itself that nothing has been changed or removed.

Rationale: Transparency the community cannot check is a promise, not evidence.

Maturity descriptors for IDG-TEC-011
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The community can ask for and receive the access record for its data.
IDG-ML2Access reports and digests of the audit log are published to the community on a schedule.
IDG-ML3The community can verify an export of the log against an anchored digest with its own tools.

Evidence types: report, audit_log, system_check

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: The audit chain can be exported and verified offline against a digest, and the verify scripts check that. The governance worker can publish per-custodian-group access reports and a digest of the chain head to an export directory, creating each file once without overwriting it.

Implementation paths: packages/graph/src/access-transparency.ts, packages/discovery/src/governance-worker.ts

Automated checks: @blaksmith/discovery governance-verify, @blaksmith/graph audit-chain-verify

Honest gaps: The digest comes from the operator's own database and is written as an ordinary file, so it is not anchored outside the operator's control unless the deployment adds immutable storage. Reports and digests are only published when the operator mounts an export directory. Nothing in the product calls the chain export, and the export covers the whole tenant, so giving it to one community would disclose other communities' events. There is no in-app route for the community to fetch or verify anything.

Framework crosswalks & departures (3)
  • NIST SP 800-53 Rev. 5 AU-9(2) supports
  • TRUST Principles for digital repositories transparency supports The community can verify the audit record against a digest the operator does not control.
  • Information Security Manual (ISM) no equivalent No control gives the community the data is about a way to verify the audit record.
IDG-TEC-012 Stage 4: Store & Protect provisional · v1 Audience: both Automated checks

Data residency onshore by default

Applies to: internal sensitive protected restricted CARE A3 CARE E1
Control

Indigenous data, its backups and its keys stay in the jurisdiction the community agreed, which defaults to Australia. Deployments outside the agreed regions are refused, and data is not sent to services in other jurisdictions without the community's agreement.

Rationale: Where data is held decides which laws can reach it. Communities need to know and agree where that is.

Maturity descriptors for IDG-TEC-012
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The hosting region is documented and agreed with the community.
IDG-ML2Infrastructure fails to deploy outside the agreed regions, including backups and keys.
IDG-ML3Every service that processes the data, including AI and support tools, is checked against the agreed jurisdiction before use.

Evidence types: configuration, agreement, system_check

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: The CDK app fails synthesis outside an allow-listed region, Sydney by default, and CI asserts the guard fires. Terraform has the same allow-list. Records can carry a residency that blocks sending them to an external AI model when cross-border transfer is not permitted.

Implementation paths: infra/aws/cdk/lib/region-guard.ts, infra/aws/terraform/versions.tf, infra/aws/terraform/variables.tf, packages/ai/src/governance.ts, .github/workflows/ci.yml

Automated checks: packages/core/src/classification/classification.test.ts

Honest gaps: The community-held key module has no region guard. At runtime residency only blocks external AI processing, and no automated test covers that refusal. Records have no residency by default, and the agreement's residency term is not enforced.

Framework crosswalks & departures (4)
  • Information Security Manual (ISM) ISM-1572 partial Regions are documented in contracts. IDG defaults to Australia and needs the community to agree.
  • NIST SP 800-53 Rev. 5 SA-9(5) partial Locations set by the organisation. IDG defaults to Australia and needs the community to agree.
  • NIST SP 800-53 Rev. 5 CM-12 supports
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme APP 8 partial Safeguards for overseas disclosure. IDG keeps data in the agreed jurisdiction.
IDG-TEC-013 Stage 4: Store & Protect provisional · v2 Audience: both Manual / Organisational

Sub-processors are disclosed

Applies to: internal sensitive protected restricted CARE R1 CARE A3
Control

The organisation tells the community which third parties host, process or support its data, where they are, and what they can access, and tells the community before adding or changing one.

Rationale: A community cannot agree to where its data goes if it does not know who else handles it.

Maturity descriptors for IDG-TEC-013
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1A current list of sub-processors, their locations and their access is available to the community.
IDG-ML2The community is told before a sub-processor is added or changed, and can object.
IDG-ML3The community's agreement is needed before a new sub-processor can handle its data.

Evidence types: register, agreement, policy

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (6)
  • Information Security Manual (ISM) ISM-1637 partial A register for the organisation. IDG requires disclosure to the community.
  • Information Security Manual (ISM) ISM-1572 supports
  • NIST SP 800-53 Rev. 5 SA-9 partial Oversight of providers by the organisation. IDG requires disclosure to the community.
  • NIST Cybersecurity Framework (CSF) 2.0 GV.SC-07 supports
  • Protective Security Policy Framework (PSPF) 40 supports
  • TRUST Principles for digital repositories transparency supports The community is told who hosts and processes its data. TRUST asks for this to be public, and IDG asks for it to go to the community.
IDG-TEC-014 Stage 6: Share & Publish provisional · v3 Audience: both Automated checks

Exports only under an agreement, with protocols attached

Applies to: internal sensitive protected restricted CARE A3 CARE R1 FAIR R1.1 FAIR R1.2
Control

Indigenous data leaves the system only for a person and purpose covered by an active agreement, in a format the agreement allows. Every export carries the data's classification, protocols, labels and agreement, and is recorded and traceable to the person who made it.

Rationale: Exports are where data leaves the controls that protect it. If protocols do not travel with the data, the recipient has no way to respect them.

Maturity descriptors for IDG-TEC-014
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Exports of Indigenous data are approved and recorded.
IDG-ML2Exports carry classification, protocols and agreements, refuse material that would lose its protocols, and are watermarked for outside parties.
IDG-ML3The system refuses any export not covered by an active agreement for that recipient, scope and format.

Evidence types: audit_log, system_check, agreement

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Trusted dataset sharing packages are built only under an active, custodian-signed data sharing agreement, scoped to the agreement's dataset and allowed formats, sealed for the recipient and carrying classification, protocols, labels and agreement metadata with a fresh consent and expiry check on download. Repatriation packages include only records the person may read with protocols attached, refuse a heritage export that would strip protocols, and write an audit event. Explorer data exports are capped at 200 records and watermarked for anyone under an engagement; proponents cannot export, and consultants cannot export culturally bound or encrypted material.

Implementation paths: packages/graph/src/dataset-package.ts, packages/graph/src/sharing-agreement.ts, packages/graph/src/repatriation.ts, packages/core/src/governance/export-package.ts, packages/graph/src/explorer-export.ts

Automated checks: packages/graph/src/dataset-package.test.ts, packages/graph/src/repatriation.test.ts, packages/graph/src/explorer-export.test.ts

Honest gaps: Direct Explorer data exports and repatriation exports for internal users not under an engagement are not gated by an active sharing agreement. Explorer image exports carry no classification, protocols, labels, agreements or watermark.

Framework crosswalks & departures (10)
  • NIST SP 800-53 Rev. 5 AC-21 partial Sharing decisions by the organisation. IDG requires an active agreement and protocols in every export.
  • NIST SP 800-53 Rev. 5 AC-3(9) partial Controlled release. IDG requires an active agreement and protocols in every export.
  • NIST SP 800-53 Rev. 5 AC-4 supports
  • Protective Security Policy Framework (PSPF) 77 partial An agreement before sharing. IDG adds allowed formats and protocols in every export.
  • FAIR Guiding Principles for scientific data management and stewardship R1.1 partial Every export carries the agreement that sets its terms of use. IDG also limits each export to a recipient and purpose the agreement covers.
  • FAIR Guiding Principles for scientific data management and stewardship R1.2 supports Every export is recorded and traceable to the person who made it.
  • Information Security Manual (ISM) ISM-0663 supports
  • Information Security Manual (ISM) ISM-0661 partial A person is accountable for each transfer. IDG also requires an active agreement and carries the data's protocols with every export.
  • Information Security Manual (ISM) ISM-1187 supports IDG attaches each record's classification and protocols to every export. It does not require a manual check of markings.
  • Information Security Manual (ISM) ISM-1586 partial Logs every import and export. IDG-TEC-014 records exports only, and adds the agreement each one was made under.
IDG-TEC-015 Stage 6: Share & Publish provisional · v1 Audience: both Automated checks

Presentation controls on display and export

Applies to: sensitive protected restricted Protocol-bound only CARE E1 CARE R3
Control

Where a community's protocol requires it, the system generalises the location of sensitive places, suppresses names and images of people who have died, and shows required warnings and attribution, on every screen and in every export.

Rationale: Showing a sacred site's exact location, or the image of someone who has passed, can cause real harm, even to people allowed to know the record exists.

Maturity descriptors for IDG-TEC-015
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Staff follow written rules for showing locations, deceased persons and warnings.
IDG-ML2The system applies generalisation, suppression, warnings and attribution on display.
IDG-ML3The same controls apply to every export and API, at a level of detail the community sets.

Evidence types: configuration, system_check

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.); contextual (Data that is contextual and disaggregated (available and accessible at individual, community and First Nations levels).)

BlakSmith worked example: Sacred site geometry is generalised to a grid cell, by default 10 kilometres or the community's chosen size, which the verify script checks with a 25 kilometre cell. Dataset packages filter sacred site records through a strict property allowlist and drop coordinate-shaped values before release. Reads of protocol-bound records suppress set property keys for deceased persons' names, and add access warnings and attribution.

Implementation paths: packages/graph/src/spatial.ts, packages/graph/src/location.ts, packages/graph/src/classified-read.ts, packages/core/src/classification/classification.ts

Automated checks: packages/core/src/classification/classification.test.ts, packages/graph/src/location.test.ts, @blaksmith/graph spatial-verify

Honest gaps: Generalisation on interactive reads covers stored geometries for the sacred site protocol, while property-level coordinate filtering runs on dataset packages rather than every interactive read. Suppression removes a fixed list of property keys, and a deceased person's story, images and voice are removed only when the name is also suppressed. The community's cell size can only be set outside the product.

Framework crosswalks & departures (2)
  • NIST SP 800-53 Rev. 5 AC-16(5) supports
  • Information Security Manual (ISM) no equivalent No control generalises locations or suppresses content about people who have died.
IDG-TEC-016 Stage 7: Retain, Return & Destroy provisional · v3 Audience: both Automated checks

Retention limits and verified purge, including backups

Applies to: public internal sensitive protected restricted CARE E1 CARE E3 FAIR: CARE precedence
Control

Indigenous data and records about access to it are kept only as long as the agreement and the law require. At the end of that time they are purged by a scheduled process, the purge is recorded, and backups expire or are purged within a stated time.

Rationale: Data kept past its purpose is still at risk, and still outside the community's control.

Maturity descriptors for IDG-TEC-016
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1A retention schedule covers each kind of Indigenous data and its backups.
IDG-ML2A scheduled process purges data at the end of its retention period, and backups expire within a stated time.
IDG-ML3Each purge is recorded in the tamper-evident log, verified, and reapplied after any restore from backup.

Evidence types: policy, configuration, audit_log, system_check

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: An hourly worker job purges expired sessions and ingestion ledger rows older than 90 days. The retention document sets out the schedule for each table, and automated database backups are kept for 35 days.

Implementation paths: packages/graph/src/retention.ts, apps/worker/src/retention-job.ts, apps/worker/src/server.ts, docs/data-retention.md, infra/aws/terraform/data.tf

Automated checks: packages/graph/src/retention.test.ts

Honest gaps: Only sessions and ingestion ledger rows are purged; the rest of the schedule is policy. Events and version snapshots, which include plaintext names, are kept with no end date. Evidence objects are under a seven year compliance object lock that no one can shorten, so they cannot be purged at the end of an agreement or on request, and the documents bucket has no expiry. The production database keeps a final snapshot with no expiry, and automated backups are not deleted with it. The purge is logged, not written to the audit chain. The retention verify script checks the selector without a database and is not run in CI. No restore drill has been run, and reapplying erasures after a restore is manual.

Framework crosswalks & departures (9)
  • NIST SP 800-53 Rev. 5 SI-12 partial Retention set by law and policy. IDG adds limits set by the agreement and verified purge.
  • NIST SP 800-53 Rev. 5 SI-12(3) partial Disposal after retention. IDG adds recording and verifying each purge.
  • Information Security Manual (ISM) ISM-1511 supports
  • Essential Eight Maturity Model Regular backups supports
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme APP 11 partial Destroy or de-identify when no longer needed. IDG adds backups and a recorded, verified purge.
  • NIST Cybersecurity Framework (CSF) 2.0 PR.DS-11 supports
  • Information Security Manual (ISM) ISM-1547 supports
  • FAIR Guiding Principles for scientific data management and stewardship no equivalent FAIR A2 asks for metadata to stay accessible after the data is gone. IDG purges the data and the records about access to it when the agreement ends. The destruction attestation (IDG-PRC-010) is what remains.
  • TRUST Principles for digital repositories no equivalent TRUST asks repositories to preserve data for the long term. IDG requires data to be purged when its agreement ends, or destroyed when the community asks.
IDG-TEC-017 Stage 5: Access, Use & AI provisional · v1 Audience: both Automated checks

AI and model training restrictions

Applies to: public internal sensitive protected restricted CARE A3 CARE E3
Control

Indigenous data is not used to train or tune AI models, and is not sent to an AI service, unless the community has agreed to that use. Culturally restricted material is never placed in search indexes or embeddings that AI features read from without that agreement.

Rationale: Once knowledge is in a model it cannot be taken back out, and the model can surface it to anyone.

Maturity descriptors for IDG-TEC-017
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Policy prohibits AI training on, or AI processing of, Indigenous data without agreement.
IDG-ML2Systems refuse to send restricted material to external AI services and leave it out of embeddings.
IDG-ML3Every AI feature, local or external, checks the agreement and consent before use, and the community can see where AI was used.

Evidence types: policy, configuration, system_check

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Culturally bound, Local Contexts labelled and existence-hidden records are not embedded. Sending material to an external model is refused when residency forbids cross-border transfer, when an agreement forbids AI use, or when culturally bound material lacks AI processing consent. Agent conversations take on the strictest classification of what they read.

Implementation paths: packages/ai/src/governance.ts, packages/search/src/search.ts, packages/agents/src/loop.ts

Automated checks: @blaksmith/search verify

Honest gaps: There is no training pipeline, so the no AI training term in practice means no AI processing. Local chat and agent models get no check at all. With a local embedding model, material under a no AI term and sensitive material without a cultural protocol are still embedded, and the embedded text is stored in plaintext. The external check ignores the statutory overlay purpose bans, agreement purpose lists and the derived consent flag. No automated test covers the external refusal or the classification of agent conversations; the search verify script checks only that protocol-bound records are not embedded.

Framework crosswalks & departures (2)
  • Information Security Manual (ISM) ISM-2074 supports
  • Information Security Manual (ISM) ISM-2112 supports
ASR

Guidelines for Assurance

5 proposed provisional controls in domain ASR

IDG-ASR-001 Stage 8: Measure & Assure provisional · v1 Audience: both Automated checks

Regular CARE and FAIR maturity self-assessment with community review

Applies to: public internal sensitive protected restricted CARE A2 CARE R1 CARE E2

Applies across every domain and lifecycle stage held in scope. See docs/idg/self-assessment.md for scoring rules and reassessment triggers.

Control

The organisation evaluates its Indigenous data handling practices against this catalogue and the CARE and FAIR principles at least once every 12 months, and whenever a new dataset, recipient, agreement change or incident enters scope. An accountable officer attests to the self-assessment, records it in the tamper-evident audit log, and provides it to the affected community for independent review.

Rationale: Policies that are never measured drift away from practice. A strict weakest-link maturity score paired with community review shows where protection is real and where work remains, without pretending that self-assessment is certification.

Maturity descriptors for IDG-ASR-001
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The organisation completes a documented self-assessment across all applicable domains at least once every 12 months, signed by the accountable officer with supporting evidence for every control above IDG-ML0.
IDG-ML2Each self-assessment is recorded in the audit chain, provided to the affected community for review with its review status tracked, and re-run after major agreement, dataset or incident triggers.
IDG-ML3Reassessment reminders are triggered automatically when intervals lapse, agreements change or a community queries or rejects a prior assessment, and remediation plans are tracked openly with the community.

Evidence types: attestation, report, audit_log, meeting_record

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.); control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.)

BlakSmith worked example: The IDG package generates fillable YAML and CSV self-assessment templates from the live catalogue, validates completeness and fixed non-certification attestation wording, scores each domain by its weakest applicable control, and records the digest, scores and reported community review status in the tenant's hash-chained audit log while closing open reassessment reminders.

Implementation paths: packages/idg/src/assessment.ts, packages/idg/src/assessment-cli.ts, docs/idg/self-assessment.md

Automated checks: packages/idg/src/assessment.test.ts

Honest gaps: Community review status is reported by the organisation rather than entered directly by the community. New datasets, new recipients, incidents and catalogue version bumps are not yet detected automatically as reassessment triggers by the governance worker.

Framework crosswalks & departures (3)
  • Framework for Governance of Indigenous Data G4.4 partial The Framework asks APS agencies to evaluate data governance practices using FAIR and CARE. IDG adds a defined maturity scale (IDG-ML0 to IDG-ML3), weakest-link scoring, accountable-officer attestation, audit-chain recording and community review.
  • ISO/IEC 38505-1: Governance of data, application of ISO/IEC 38500 to the governance of data oversight-assurance supports
  • TRUST Principles for digital repositories transparency supports Provides structured evidence of governance practice to the community the data is about.
IDG-ASR-002 Stage 8: Measure & Assure provisional · v1 Audience: both Automated checks

Continuous automated control evidence anchored to the audit chain

Applies to: internal sensitive protected restricted CARE A2 CARE R1

Automated evidence covers controls with runnable checks and reports manual controls explicitly rather than treating them as passed.

Control

Where technical controls protect Indigenous data, the organisation runs automated checks against its live or verification environment on a defined schedule, signs the resulting evidence bundle with an operator signing key, and anchors the bundle digest into the tenant's tamper-evident audit chain so gaps and regressions are visible over time.

Rationale: Point-in-time reviews miss configuration drift and code regressions. Signed, chain-linked evidence bundles tie automated test results to an exact commit, catalogue version and audit chain head without leaking underlying record content.

Maturity descriptors for IDG-ASR-002
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Automated checks exist for core technical controls and are run before releases, with results retained alongside the commit tested.
IDG-ML2Every mapped check runs in a repeatable pipeline that outputs a signed evidence bundle recording pass, fail, missing, manual and unchecked statuses, anchored to the audit chain.
IDG-ML3Evidence bundles are signed with a managed operator key, verified against a pinned public key in the governance interface, and surfaced to communities alongside any failed or missing checks.

Evidence types: system_check, audit_log, report, configuration

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: pnpm idg:evidence executes every unit test and verify script mapped across the catalogue, builds a canonical JSON bundle excluding raw check output, signs it with Ed25519, records the tenant's audit chain head in the bundle, and appends an idg.evidence.recorded event carrying the bundle SHA-256 digest to the same audit chain.

Implementation paths: packages/idg/src/evidence.ts, packages/idg/src/evidence-cli.ts, packages/graph/src/audit-chain.ts

Automated checks: packages/idg/src/evidence.test.ts

Honest gaps: Evidence runs are executed manually against a seeded verification database rather than on an automatic production schedule. Without an operator signing key file, bundles use an ephemeral key and are marked unverified in the web interface. Communities do not yet have a direct portal view of evidence bundles.

Framework crosswalks & departures (4)
  • NIST SP 800-53 Rev. 5 CA-7(1) supports
  • NIST Cybersecurity Framework (CSF) 2.0 PR.PS-04 supports
  • TRUST Principles for digital repositories transparency supports Produces verifiable, signed evidence of technical control checks without claiming certification or endorsement.
  • ISO/IEC 38505-1: Governance of data, application of ISO/IEC 38500 to the governance of data oversight-assurance supports
IDG-ASR-003 Stage 8: Measure & Assure provisional · v1 Audience: both Automated checks

Community data inventory and FAIR metadata quality verification

Applies to: public internal sensitive protected restricted CARE A2 CARE C2 CARE R1 FAIR F2 FAIR R1 FAIR R1.2
Control

The organisation maintains a current inventory of all Indigenous data assets it holds, recording provenance, sensitivity classification, cultural protocols, Local Contexts labels, storage location, consent status, active agreements and end-of-use terms, and provides each community with an accessible inventory of data relating to it without exposing existence-hidden material to unauthorised people.

Rationale: A community cannot exercise authority over data it does not know exists. Maintaining a structured, protocol-aware inventory also measures FAIR metadata richness and provenance while upholding CARE authority and protection rules.

Maturity descriptors for IDG-ASR-003
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The organisation maps every repository and dataset holding Indigenous data and can give each community a plain-language list of what is held about it on request.
IDG-ML2Inventories are generated from live system metadata with provenance, protocols, consent, agreements and outside-party access included, and are verified for completeness at least annually.
IDG-ML3Communities receive accessible, protocol-aware inventories on an agreed schedule or on demand, and metadata quality defects such as missing provenance, consent or review dates are measured and remediated continuously.

Evidence types: register, report, system_check, audit_log

Maiam nayri Wingara: contextual (Data that is contextual and disaggregated (available and accessible at individual, community and First Nations levels).); accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: The graph package builds a per-custodian-group community data inventory and renders it as accessible WCAG 2.2 AA HTML showing each permitted record's sensitivity, cultural protocols, labels, residency, consent status, active agreements, end-of-use terms and outside-party recipients, while honouring existence hiding.

Implementation paths: packages/graph/src/community-inventory.ts, packages/graph/src/community-inventory-html.ts, packages/graph/src/community-sharing-report.ts

Automated checks: packages/graph/src/community-inventory.test.ts, packages/graph/src/community-sharing-report.test.ts

Honest gaps: Community inventories are generated by operators or through authenticated tenant API routes rather than delivered through an independent community-directed portal (issue #236). Automated metadata completeness scoring across all FAIR fields is not yet built.

Framework crosswalks & departures (6)
  • Framework for Governance of Indigenous Data G3.1 partial The Framework asks APS agencies to map Indigenous data assets and share that mapping in an accessible format. IDG adds protocol-aware filtering, consent and agreement tracking, and ongoing metadata verification.
  • Framework for Governance of Indigenous Data G3.5(a) supports
  • FAIR Guiding Principles for scientific data management and stewardship F2 supports Verifies that records carry rich governance and descriptive metadata while honouring cultural protocol restrictions.
  • FAIR Guiding Principles for scientific data management and stewardship R1 supports
  • FAIR Guiding Principles for scientific data management and stewardship R1.2 supports Checks that provenance, consent and agreement lineage remain attached to each data asset.
  • TRUST Principles for digital repositories transparency supports
IDG-ASR-004 Stage 8: Measure & Assure provisional · v1 Audience: both Manual / Organisational

Periodic verification of data transfer logs and backup restoration drills

Applies to: internal sensitive protected restricted CARE E1 CARE A3
Control

The organisation verifies data transfer and export logs at least monthly against active community agreements, and tests restoration from backups on a regular schedule to confirm both recovery readiness and that prior cryptographic erasures, consent revocations and purges are reapplied without restoring destroyed Indigenous data.

Rationale: Unreviewed export logs fail to catch unauthorised transfers, and untested backup restores risk either losing community data or silently resurrecting records a community ordered destroyed.

Maturity descriptors for IDG-ASR-004
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Transfer and export logs are sampled and checked against active agreements at least quarterly, and a written backup restoration procedure includes reapplying erasures and purges.
IDG-ML2Transfer logs are partially verified at least monthly with anomalies investigated and recorded, and backup restoration is tested at least annually in a non-production environment including erasure and purge replay.
IDG-ML3Automated checks reconcile every export and download against active sharing agreements and alert on exceptions, and scheduled restore drills prove destroyed keys and purged records remain unreadable after recovery, with drill results reported to affected communities.

Evidence types: audit_log, report, procedure, system_check

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.); accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (4)
  • Information Security Manual (ISM) ISM-1294 partial The ISM requires data transfer logs to be partially verified at least monthly. IDG adds reconciliation against active community sharing agreements and reporting exceptions to custodians.
  • Information Security Manual (ISM) ISM-1515 partial The ISM requires testing restoration from backups in disaster recovery exercises. IDG adds verifying that cryptographic erasures and community-ordered purges stay effective after restore.
  • NIST Cybersecurity Framework (CSF) 2.0 PR.DS-11 supports
  • Essential Eight Maturity Model Regular backups supports
IDG-ASR-005 Stage 8: Measure & Assure provisional · v1 Audience: both Manual / Organisational

Independent partnership and governance health check

Applies to: sensitive protected restricted CARE R1 CARE E2 CARE C3
Control

At an interval agreed with the communities whose data it holds, the organisation conducts an impartial partnership and governance health check carried out by an independent reviewer acceptable to the communities, evaluating whether agreements, cultural protocols, benefit commitments and governance bodies work in practice. Findings and remediation actions are shared transparently with the communities.

Rationale: Internal self-assessments reflect the organisation's own view. Impartial external review gives communities an independent check on whether agreed governance practices and relationships are honoured over time.

Maturity descriptors for IDG-ASR-005
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The organisation and community agree terms for periodic review of their data governance relationship and document any concerns raised.
IDG-ML2An impartial reviewer acceptable to the community conducts a partnership health check on an agreed cycle covering agreements, protocols and benefit delivery, and delivers findings to both parties.
IDG-ML3Independent health checks include Indigenous-led assessment, track remediation of prior findings to closure, and feed directly into the governing body's oversight under IDG-GOV-004.

Evidence types: report, meeting_record, interview, agreement

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.); control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (3)
  • Framework for Governance of Indigenous Data G1.6 partial The Framework asks APS agencies to conduct regular partnership health checks with external, impartial monitoring. IDG extends this to any organisation holding Indigenous data, requires community acceptance of the reviewer and shares results directly with the community.
  • ISO/IEC 38505-1: Governance of data, application of ISO/IEC 38500 to the governance of data oversight-assurance supports
  • NIST SP 800-53 Rev. 5 CA-7(1) partial Covers independent assessment chosen by the organisation. IDG requires community acceptance of the reviewer and sharing findings with the community.
CON

Guidelines for Consuming entity

13 proposed provisional controls in domain CON

IDG-CON-001 Stage 5: Access, Use & AI provisional · v2 Audience: consumer Manual / Organisational

A named accountable officer

Applies to: internal sensitive protected restricted CARE R1 CARE A3
Control

The receiving organisation names a senior person who is accountable for how it handles the data, who signs the agreement and any attestations, and who the community can contact directly. Responsibility cannot be passed to a contractor or a project team.

Rationale: When something goes wrong, the community needs one person who is answerable and has the authority to act.

Maturity descriptors for IDG-CON-001
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1An accountable officer is named in the agreement, with contact details the community holds.
IDG-ML2The accountable officer signs the agreement and every attestation, and a replacement is named before they leave.
IDG-ML3The accountable officer reports to the community at agreed intervals on how the data is being used.

Evidence types: agreement, attestation, register

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (3)
  • Protective Security Policy Framework (PSPF) 7 partial Accountability inside the entity. IDG adds a named contact the community can reach.
  • NIST Cybersecurity Framework (CSF) 2.0 GV.RR-01 partial Leadership accountability. IDG adds signing the agreement and attestations.
  • ISO/IEC 38505-1: Governance of data, application of ISO/IEC 38500 to the governance of data governing-body-accountability supports Both place accountability for the use of data with senior people. IDG-CON-001 names one accountable officer for a specific agreement, who the community can contact directly.
IDG-CON-002 Stage 5: Access, Use & AI provisional · v1 Audience: consumer Manual / Organisational

Only approved users

Applies to: internal sensitive protected restricted CARE A3 CARE E1
Control

Only people named on an approved users list may access the data. The community or its delegate approves each person before access, and the list is kept current, with people removed as soon as they no longer need access.

Rationale: A dataset shared with an organisation is often passed around inside it. A named list keeps access to the people the community agreed to.

Maturity descriptors for IDG-CON-002
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1A list of people with access is kept and given to the community.
IDG-ML2Each person is approved before access, and the list is reviewed at least every six months.
IDG-ML3Access is technically limited to the approved list, and changes are notified to the community.

Evidence types: register, configuration, audit_log

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (3)
  • Information Security Manual (ISM) ISM-0405 partial Validation by the organisation. IDG requires approval by the community.
  • NIST SP 800-53 Rev. 5 AC-2 partial Account approval by the organisation. IDG requires approval by the community.
  • Protective Security Policy Framework (PSPF) 75 partial Need-to-know only. IDG requires a named list approved by the community.
IDG-CON-003 Stage 4: Store & Protect provisional · v1 Audience: consumer Manual / Organisational

A secure environment matched to the data

Applies to: internal sensitive protected restricted CARE E1

For protected and restricted data, a dedicated environment such as a secure research platform is expected.

Control

The data is held and used only in an environment with security that matches its sensitivity: access control, encryption, logging and backups the community has agreed to. It is not copied to personal devices, personal email or unapproved cloud services.

Rationale: Data that leaves a secure environment, even briefly, is outside every other control in the agreement.

Maturity descriptors for IDG-CON-003
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The environment where the data will be held is described in the agreement.
IDG-ML2The environment has access control, encryption at rest, logging and backups, with no personal device or unapproved cloud use, confirmed before data is released.
IDG-ML3The environment has been independently assessed, and the data cannot be copied out of it without approval.

Evidence types: configuration, attestation, report

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (3)
  • Information Security Manual (ISM) ISM-1080 supports
  • NIST Cybersecurity Framework (CSF) 2.0 PR.DS-01 supports
  • NIST Cybersecurity Framework (CSF) 2.0 PR.DS-02 supports
IDG-CON-004 Stage 5: Access, Use & AI provisional · v1 Audience: consumer Manual / Organisational

Use only for the agreed purpose

Applies to: internal sensitive protected restricted CARE A3 CARE E1
Control

The data is used only for the purpose in the agreement. Any other use, including a new research question, needs a new approval from the community first.

Rationale: Purpose is the line the community drew when it agreed to share.

Maturity descriptors for IDG-CON-004
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Everyone with access knows the agreed purpose and has agreed in writing to keep to it.
IDG-ML2New uses are put to the community for approval before work starts, and the decision is recorded.
IDG-ML3Use of the data is logged against the agreed purpose, and the log is available to the community.

Evidence types: agreement, attestation, register

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); relevant (Data that is relevant and empowers sustainable self-determination and effective self-governance.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (2)
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme APP 6 partial APP 6 allows some uses beyond the primary purpose without consent.
  • NIST SP 800-53 Rev. 5 PT-3 partial Purposes set by the organisation, not agreed with the community.
IDG-CON-005 Stage 6: Share & Publish provisional · v1 Audience: consumer Manual / Organisational

No onward sharing

Applies to: internal sensitive protected restricted CARE A3 CARE R1
Control

The receiving organisation does not share the data, or anything derived from it, with anyone outside the approved users, unless the agreement allows it and the community approves the specific recipient. Any approved onward recipient is bound by the same terms.

Rationale: Each onward share takes the data further from the community's sight.

Maturity descriptors for IDG-CON-005
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Staff and contractors have agreed in writing not to share the data onward.
IDG-ML2Any onward share has the community's written approval and is recorded.
IDG-ML3Technical controls prevent the data being sent outside the approved environment.

Evidence types: agreement, attestation, configuration

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (3)
  • NIST SP 800-53 Rev. 5 PS-6 partial Access agreements signed by users. IDG adds community approval for each onward recipient.
  • NIST SP 800-53 Rev. 5 AC-21 supports
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme APP 6 supports
IDG-CON-006 Stage 6: Share & Publish provisional · v2 Audience: consumer Manual / Organisational

No re-identification and no unapproved linkage

Applies to: internal sensitive protected restricted CARE E1 CARE E2
Control

The receiving organisation does not try to identify any person, family or community from the data, and does not link it with other data unless the community approved that linkage. If someone is identified by accident, the organisation stops, does not use or share the result, and tells the community.

Rationale: Small populations are easy to identify even without names, and linkage multiplies the risk.

Maturity descriptors for IDG-CON-006
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Everyone with access has agreed in writing not to re-identify or link the data.
IDG-ML2Approved linkages are recorded with the community's approval, and accidental identification is reported.
IDG-ML3Outputs are checked for re-identification risk before they leave the environment.

Evidence types: agreement, attestation, procedure

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (2)
  • NIST SP 800-53 Rev. 5 SI-19 supports
  • Framework for Governance of Indigenous Data G4.12 supports Bars a recipient from identifying a family or community as well as a person, which protects group privacy for data already shared.
IDG-CON-007 Stage 5: Access, Use & AI provisional · v1 Audience: consumer Manual / Organisational

No AI training or processing without agreement

Applies to: internal sensitive protected restricted CARE A3 CARE E3
Control

The data is not used to train, tune or prompt any AI model, and is not entered into any AI tool or service, unless the agreement allows that specific use.

Rationale: Once data is inside a model or an AI service it cannot be recalled, and it may resurface anywhere.

Maturity descriptors for IDG-CON-007
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Everyone with access has agreed in writing not to use the data with AI tools unless the agreement allows it.
IDG-ML2AI tools are blocked or restricted in the environment where the data is held.
IDG-ML3Any permitted AI use is limited to tools and locations the community approved, and is logged.

Evidence types: policy, configuration, attestation

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (1)
  • Information Security Manual (ISM) ISM-2074 partial A general AI usage policy. IDG bans AI use of the data unless the agreement allows it.
IDG-CON-008 Stage 7: Retain, Return & Destroy provisional · v1 Audience: consumer Manual / Organisational

Tell the community about any breach

Applies to: internal sensitive protected restricted CARE R1 CARE E1
Control

If the data is lost, accessed without authority, disclosed or used outside the agreement, the receiving organisation tells the community and the data custodian as soon as practicable and within the time in the agreement, and works with them on the response. Telling a regulator does not replace telling the community.

Rationale: The community can only protect itself from harm it knows about.

Maturity descriptors for IDG-CON-008
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The organisation's incident procedure includes notifying the community and the custodian.
IDG-ML2Notification times are set in the agreement and tested in an exercise.
IDG-ML3The community is involved in investigating and reviewing every incident involving its data.

Evidence types: procedure, report, agreement

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (3)
  • Information Security Manual (ISM) ISM-1880 partial Reporting to customers. IDG requires telling the community and the custodian.
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme NDB partial Covers serious harm to individuals only.
  • NIST Cybersecurity Framework (CSF) 2.0 RS.CO-02 partial Stakeholders are chosen by the organisation.
IDG-CON-009 Stage 7: Retain, Return & Destroy provisional · v1 Audience: consumer Manual / Organisational

Destroy or return the data at the end, and attest to it

Applies to: internal sensitive protected restricted CARE A1 CARE R1
Control

When the agreement ends, or the community asks, the receiving organisation destroys or returns the data as agreed, including copies, backups and derived data, and the accountable officer signs an attestation saying what was destroyed or returned, how and when.

Rationale: Without an attestation, the community has no assurance its data is really gone.

Maturity descriptors for IDG-CON-009
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The organisation knows where every copy of the data is held.
IDG-ML2At the end, every copy, backup and derived file is destroyed or returned and the accountable officer signs an attestation.
IDG-ML3Destruction is independently verified or evidenced by system records, and the attestation is given to the community.

Evidence types: attestation, register, procedure

Maiam nayri Wingara: control (Exercise control of the data ecosystem including creation, development, stewardship, analysis, dissemination and infrastructure.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (3)
  • NIST SP 800-53 Rev. 5 MP-6(1) partial Tracking media sanitisation. IDG adds backups, derived data and an attestation to the community.
  • Protective Security Policy Framework (PSPF) 73 partial Secure disposal. IDG adds an attestation to the community.
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme APP 11 partial Destroy or de-identify when no longer needed. IDG adds return or destruction on request.
IDG-CON-010 Stage 6: Share & Publish provisional · v2 Audience: consumer Manual / Organisational

Community review before publication

Applies to: internal sensitive protected restricted CARE A3 CARE E1 CARE R3
Control

Before publishing or presenting anything that uses the data, the receiving organisation gives the community the time agreed to review it, and acts on the community's concerns as the agreement sets out, including any right to withhold culturally sensitive material.

Rationale: Publication is permanent. The community should see how it is represented before everyone else does.

Maturity descriptors for IDG-CON-010
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1The agreement says which outputs the community reviews and how long it has.
IDG-ML2Every output is sent for review before release, and the community's response is recorded.
IDG-ML3The community is involved in interpreting the findings, not only reviewing them.

Evidence types: agreement, meeting_record, register

Maiam nayri Wingara: relevant (Data that is relevant and empowers sustainable self-determination and effective self-governance.); protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (3)
  • Framework for Governance of Indigenous Data G4.8(b) supports Community review before publication covers the interpretation and dissemination phases only.
  • NIST SP 800-53 Rev. 5 no equivalent No control gives a community review of publications before release.
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme no equivalent No principle gives a community review of publications before release.
IDG-CON-011 Stage 6: Share & Publish provisional · v1 Audience: consumer Manual / Organisational

Benefit sharing and attribution

Applies to: internal sensitive protected restricted CARE C1 CARE C3 CARE R2
Control

The receiving organisation delivers the benefits to the community set out in the agreement, credits the community as the community asks, and shares findings back in a form the community can use.

Rationale: Data about a community should benefit that community, not only the people who use it.

Maturity descriptors for IDG-CON-011
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Benefits and attribution are written into the agreement.
IDG-ML2Benefits delivered and findings shared are recorded and reported to the community.
IDG-ML3The community helps decide what benefit means for each project, and reviews whether it was delivered.

Evidence types: agreement, report, register

Maiam nayri Wingara: relevant (Data that is relevant and empowers sustainable self-determination and effective self-governance.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (2)
  • NIST SP 800-53 Rev. 5 no equivalent No control addresses benefit to the people the data is about.
  • Privacy Act 1988: Australian Privacy Principles and the Notifiable Data Breaches scheme no equivalent No principle addresses benefit sharing.
IDG-CON-012 Stage 5: Access, Use & AI provisional · v1 Audience: consumer Manual / Organisational

Recipient staff are trained before data is released

Applies to: internal sensitive protected restricted CARE R1 CARE E1
Control

Before the data is released, the receiving organisation shows that everyone on its approved users list has completed the cultural competency and data sovereignty training in IDG-PPL-003, and has been briefed on the specific conditions in this agreement.

Rationale: Recipients often have the least context about the community whose data they hold.

Maturity descriptors for IDG-CON-012
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Approved users complete training before access.
IDG-ML2Training records are kept and provided to the community on request, and refreshed at least every 12 months.
IDG-ML3Training is designed or delivered with the community or an Indigenous-led provider.

Evidence types: training_record, attestation

Maiam nayri Wingara: protective (Data that is protective and respects our individual and collective interests.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (3)
  • Information Security Manual (ISM) ISM-0252 partial Cyber security awareness only, not cultural competency.
  • Protective Security Policy Framework (PSPF) 24 partial Security awareness only, not cultural competency.
  • NIST SP 800-53 Rev. 5 AT-2 partial Security and privacy literacy only.
IDG-CON-013 Stage 8: Measure & Assure provisional · v2 Audience: consumer Manual / Organisational

Access records available to the community

Applies to: sensitive protected restricted CARE A2 CARE R1
Control

The receiving organisation keeps a record of who accessed the data and when, and gives it to the community or the data custodian on request.

Rationale: The community's ability to see how its data is used should not stop at the organisation that first held it.

Maturity descriptors for IDG-CON-013
Maturity LevelRequired Implementation Descriptor
IDG-ML0Not in place, or does not yet satisfy IDG-ML1.
IDG-ML1Access to the data is logged.
IDG-ML2Access logs are kept for the life of the agreement and provided on request.
IDG-ML3Access logs are reported to the community at agreed intervals without being asked.

Evidence types: audit_log, report

Maiam nayri Wingara: accountable (Data structures that are accountable to Indigenous peoples and First Nations.)

BlakSmith worked example: Manual organisational evidence required (policies, registers, meeting records or signed attestations).

Framework crosswalks & departures (3)
  • Information Security Manual (ISM) ISM-1988 partial Retention for 12 months. IDG requires sharing with the community on request.
  • NIST SP 800-53 Rev. 5 AU-11 partial Retention only. IDG requires sharing with the community on request.
  • TRUST Principles for digital repositories transparency supports The receiving organisation gives the community its access record. This goes to the community, not the public.
Appendix A · Global Indigenous Data Alliance (September 2019)

CARE Principles Coverage Matrix

Every proposed IDG control maps to one or more CARE sub-principles. No control alone satisfies a CARE principle because CARE turns on decisions communities make for themselves.

CARE sub-principles mapped to proposed IDG controls
CodeCARE Sub-PrincipleControlsMapped IDG Control IDs
C1For inclusive development and innovation3IDG-CON-011, IDG-PPL-012, IDG-PRC-014
C2For improved governance and citizen engagement2IDG-ASR-003, IDG-PRC-015
C3For equitable outcomes5IDG-ASR-005, IDG-CON-011, IDG-PRC-001, IDG-PRC-004, IDG-PRC-013
A1Recognizing rights and interests11IDG-CON-009, IDG-GOV-001, IDG-GOV-003, IDG-PPL-002, IDG-PPL-005, IDG-PRC-001, IDG-PRC-002, IDG-PRC-005, IDG-PRC-010, IDG-TEC-006, IDG-TEC-007
A2Data for governance10IDG-ASR-001, IDG-ASR-002, IDG-ASR-003, IDG-CON-013, IDG-PPL-010, IDG-PRC-013, IDG-PRC-014, IDG-PRC-015, IDG-TEC-010, IDG-TEC-011
A3Governance of data36IDG-ASR-004, IDG-CON-001, IDG-CON-002, IDG-CON-004, IDG-CON-005, IDG-CON-007, IDG-CON-010, IDG-GOV-001, IDG-GOV-002, IDG-GOV-004, IDG-GOV-005, IDG-PPL-001, IDG-PPL-002, IDG-PPL-005, IDG-PPL-007, IDG-PPL-009, IDG-PPL-011, IDG-PRC-001, IDG-PRC-003, IDG-PRC-004, IDG-PRC-005, IDG-PRC-006, IDG-PRC-007, IDG-PRC-008, IDG-PRC-011, IDG-PRC-016, IDG-TEC-001, IDG-TEC-002, IDG-TEC-003, IDG-TEC-006, IDG-TEC-008, IDG-TEC-009, IDG-TEC-012, IDG-TEC-013, IDG-TEC-014, IDG-TEC-017
R1For positive relationships23IDG-ASR-001, IDG-ASR-002, IDG-ASR-003, IDG-ASR-005, IDG-CON-001, IDG-CON-005, IDG-CON-008, IDG-CON-009, IDG-CON-012, IDG-CON-013, IDG-GOV-004, IDG-PPL-001, IDG-PPL-003, IDG-PPL-010, IDG-PRC-007, IDG-PRC-008, IDG-PRC-009, IDG-PRC-010, IDG-PRC-011, IDG-TEC-010, IDG-TEC-011, IDG-TEC-013, IDG-TEC-014
R2For expanding capability and capacity2IDG-CON-011, IDG-PPL-012
R3For Indigenous languages and worldviews3IDG-CON-010, IDG-TEC-002, IDG-TEC-015
E1For minimizing harm and maximizing benefit30IDG-ASR-004, IDG-CON-002, IDG-CON-003, IDG-CON-004, IDG-CON-006, IDG-CON-008, IDG-CON-010, IDG-CON-012, IDG-GOV-002, IDG-PPL-003, IDG-PPL-004, IDG-PPL-006, IDG-PPL-007, IDG-PPL-008, IDG-PPL-009, IDG-PPL-011, IDG-PRC-002, IDG-PRC-003, IDG-PRC-006, IDG-PRC-009, IDG-PRC-012, IDG-PRC-016, IDG-TEC-001, IDG-TEC-003, IDG-TEC-004, IDG-TEC-005, IDG-TEC-009, IDG-TEC-012, IDG-TEC-015, IDG-TEC-016
E2For justice6IDG-ASR-001, IDG-ASR-005, IDG-CON-006, IDG-GOV-005, IDG-PRC-009, IDG-PRC-012
E3For future use7IDG-CON-007, IDG-GOV-003, IDG-PRC-004, IDG-PRC-016, IDG-TEC-007, IDG-TEC-016, IDG-TEC-017
Appendix B · Wilkinson et al. (2016) & GO FAIR Foundation

FAIR Guiding Principles Coverage & CARE Precedence Matrix

IDG aligns with FAIR metadata, authorisation, provenance and community-standard principles while letting CARE take precedence wherever open indexing, indefinite metadata persistence or generic reuse licences would undermine Indigenous authority or cause cultural harm.

All 15 FAIR Guiding Principles mapped to proposed IDG controls and deliberate departures
CodeFAIR Guiding PrincipleMapped IDG Controls & CARE Precedence Notes
F1(meta)data are assigned a globally unique and persistent identifierRepository capability (optional under community direction)
F2data are described with rich metadataIDG-ASR-003 (supports)
F3metadata clearly and explicitly include the identifier of the data it describesRepository capability (optional under community direction)
F4(meta)data are registered or indexed in a searchable resourceRepository capability (optional under community direction)
CARE precedence: IDG-TEC-003 requires existence hiding for protocol-bound records.
A1(meta)data are retrievable by their identifier using a standardized communications protocolRepository capability (optional under community direction)
A1.1the protocol is open, free, and universally implementableRepository capability (optional under community direction)
A1.2the protocol allows for an authentication and authorization procedure, where necessaryIDG-TEC-008 (exceeds), IDG-TEC-009 (supports)
A2metadata are accessible, even when the data are no longer availableRepository capability (optional under community direction)
CARE precedence: IDG-TEC-007 & IDG-TEC-016 purge data/keys; only destruction attestation remains.
I1(meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representationRepository capability (optional under community direction)
I2(meta)data use vocabularies that follow FAIR principlesRepository capability (optional under community direction)
I3(meta)data include qualified references to other (meta)dataRepository capability (optional under community direction)
R1(meta)data are richly described with a plurality of accurate and relevant attributesIDG-ASR-003 (supports), IDG-TEC-001 (supports)
R1.1(meta)data are released with a clear and accessible data usage licenseIDG-PRC-001 (partial), IDG-PRC-004 (supports), IDG-TEC-002 (partial), IDG-TEC-014 (partial)
CARE precedence: IDG-PRC-001 & IDG-PRC-004 require custodian-signed agreements and fresh consent per use.
R1.2(meta)data are associated with detailed provenanceIDG-ASR-003 (supports), IDG-PRC-016 (supports), IDG-TEC-010 (supports), IDG-TEC-014 (supports)
R1.3(meta)data meet domain-relevant community standardsIDG-TEC-002 (partial)
Appendix C · ASD Information Security Manual (September 2026, OSCAL v2026.09.4)

ASD ISM Crosswalk Reference (55 of 58 Controls Mapped)

Every ISM control identifier and statement below is verified against ASD's official OSCAL catalogue (v2026.09.4) via pnpm idg:verify-sources. Note that no mapping is marked equivalent because every IDG control adds collective community obligations beyond organisational security.

Verified ASD ISM controls mapped to IDG controls
ISM IDASD ISM Control StatementMapped IDG Controls / Disposition
ISM-0072Security requirements associated with the confidentiality, integrity and availability of data are documented in contractual arrangements with service providers and regularly reviewed to ensure they remain fit for purpose.IDG-PRC-001 (supports)
ISM-0133When a data spill occurs, data owners are advised and access to the data is restricted.IDG-PRC-009 (partial)
ISM-0142The compromise or suspected compromise of cryptographic equipment or associated keying material is reported to the chief information security officer, or one of their delegates, as soon as possible after it occurs.IDG-PRC-009 (supports)
ISM-0252Cyber security awareness training is undertaken annually by all personnel and covers: [the list in the ISM]IDG-CON-012 (partial), IDG-PPL-003 (partial)
ISM-0313IT equipment sanitisation processes, and supporting IT equipment sanitisation procedures, are developed, implemented and maintained.IDG-PRC-010 (supports)
ISM-0323Media is classified to the highest sensitivity or classification of data it stores, unless the media has been classified to a higher sensitivity or classification.Unmapped gap (media-level)
ISM-0348Media sanitisation processes, and supporting media sanitisation procedures, are developed, implemented and maintained.IDG-PRC-010 (supports)
ISM-0363Media destruction processes, and supporting media destruction procedures, are developed, implemented and maintained.IDG-PRC-010 (supports)
ISM-0393Databases and their contents are classified based on the sensitivity or classification of data that they contain.IDG-TEC-001 (partial)
ISM-0405Requests for unprivileged access to systems and their resources are validated when first requested.IDG-CON-002 (partial), IDG-PPL-007 (partial)
ISM-0414Users granted access to systems and their resources are uniquely identifiable.IDG-PPL-010 (supports)
ISM-0430Access to systems and their resources are removed or suspended the same day users no longer have a legitimate requirement for access.IDG-PPL-009 (partial)
ISM-0434Personnel undergo appropriate employment screening and, where necessary, hold an appropriate security clearance before being granted access to systems and their resources.IDG-PPL-004 (partial)
ISM-0441When personnel are granted temporary access to systems and their resources, effective security controls are put in place to restrict their access to only data required for them to undertake their duties or functions.IDG-PPL-011 (partial)
ISM-0455Where practical, cryptographic equipment, applications and libraries provide a means of data recovery to allow for circumstances where the encryption key is unavailable due to loss, damage or failure.Deliberate CARE departure (see IDG-TEC-007)
ISM-0507Cryptographic key management processes, and supporting cryptographic key management procedures, are developed, implemented and maintained.IDG-PPL-005 (partial), IDG-TEC-006 (supports)
ISM-0661Human users transferring data to and from systems are held accountable for data transfers they perform.IDG-TEC-014 (partial)
ISM-0663Data transfer processes, and supporting data transfer procedures, are developed, implemented and maintained.IDG-TEC-014 (supports)
ISM-0988An accurate and consistent time source is used for event logging.IDG-TEC-010 (supports)
ISM-1059All data stored on media is encrypted using ASD-approved cryptography.IDG-TEC-004 (partial)
ISM-1080An AACA or high assurance cryptographic algorithm is used when encrypting data at rest.IDG-CON-003 (supports), IDG-TEC-004 (partial)
ISM-1139Only the latest version of TLS is used for TLS connections.IDG-TEC-005 (partial)
ISM-1173Multi-factor authentication is used to authenticate privileged human users of systems.IDG-PPL-006 (partial)
ISM-1187When manually exporting data from systems, the data is checked for unsuitable protective markings.IDG-TEC-014 (supports)
ISM-1268The need-to-know principle is enforced for database contents through the application of minimum privileges, database views, database roles and data tokenisation.IDG-TEC-008 (supports), IDG-TEC-009 (supports)
ISM-1277Data communicated between database servers and web servers is encrypted using Australian Signals Directorate-approved cryptography.IDG-TEC-005 (supports)
ISM-1294Data transfer logs for systems are partially verified at least monthly.IDG-ASR-004 (partial)
ISM-1404Unprivileged access to systems and their resources are disabled after 45 days of inactivity.IDG-PPL-009 (supports)
ISM-1405A centralised event logging facility is implemented.IDG-TEC-010 (supports)
ISM-1504Multi-factor authentication is used to authenticate human users to their organisation’s online services that process, store or communicate their organisation’s sensitive data.IDG-PPL-006 (supports)
ISM-1508Privileged access to systems and their resources is limited to only what is required for users to undertake their duties or functions.IDG-GOV-002 (exceeds), IDG-PPL-007 (partial)
ISM-1511Backups of data, applications and settings are performed and retained in accordance with business criticality and business continuity requirements.IDG-TEC-016 (supports)
ISM-1515Restoration of data, applications and settings from backups to a common point in time is tested as part of disaster recovery exercises.IDG-ASR-004 (partial)
ISM-1547Data backup processes, and supporting data backup procedures, are developed, implemented and maintained.IDG-TEC-016 (supports)
ISM-1572The regions or availability zones where data will be processed, stored and communicated, as well as a minimum notification period for any configuration changes, is documented in contractual arrangements with service providers.IDG-TEC-012 (partial), IDG-TEC-013 (supports)
ISM-1574The storage of data in a portable manner that enables backups, service migration and service decommissioning without any loss of data is documented in contractual arrangements with service providers.IDG-PRC-013 (partial)
ISM-1586Data transfer logs are used to record all data imports and exports from systems.IDG-TEC-014 (partial)
ISM-1610A method of emergency access to systems and their resources is documented and tested at least once when initially implemented and each time fundamental information technology infrastructure changes occur.IDG-GOV-002 (partial)
ISM-1611Break glass accounts are only used when normal authentication processes cannot be used.IDG-GOV-002 (exceeds)
ISM-1613Use of break glass accounts is centrally logged.IDG-GOV-002 (partial)
ISM-1637An outsourced cloud service register is developed, implemented, maintained and regularly verified.IDG-TEC-013 (partial)
ISM-1647Privileged access to systems and their resources are disabled after 12 months unless revalidated.IDG-PRC-007 (partial)
ISM-1648Privileged access to systems and their resources are disabled after 45 days of inactivity.IDG-PPL-009 (supports)
ISM-1682Multi-factor authentication used for authenticating human users of systems is phishing-resistant.IDG-PPL-006 (partial)
ISM-1735Media that cannot be successfully sanitised is destroyed prior to its disposal.IDG-PRC-010 (supports)
ISM-1781All data communicated over network infrastructure is encrypted using ASD-approved cryptography.IDG-TEC-005 (partial)
ISM-1811Backups of data, applications and settings are retained in a secure and resilient manner.IDG-TEC-004 (supports)
ISM-1815Event logs are protected from unauthorised modification and deletion.IDG-PPL-010 (supports), IDG-TEC-010 (partial)
ISM-1845When a user account is disabled, it is removed from all security group memberships.IDG-PPL-009 (supports)
ISM-1852Unprivileged access to systems and their resources is limited to only what is required for users to undertake their duties or functions.IDG-PPL-007 (partial)
ISM-1880Cyber security incidents that involve customer data are reported to customers and the public in a timely manner after they occur or are discovered.IDG-CON-008 (partial), IDG-PRC-009 (partial)
ISM-1985Event logs are protected from unauthorised access.IDG-TEC-010 (supports)
ISM-1988Event logs are retained in a searchable manner for at least 12 months.IDG-CON-013 (partial), IDG-TEC-010 (partial)
ISM-1989Event logs are retained as per minimum retention requirements for various classes of records as set out by the National Archives of Australia’s Administrative Functions Disposal Authority Express (AFDA Express) Version 2 publication.IDG-TEC-010 (partial)
ISM-2053End of life procedures for software, including procedures for software removal and the archival or destruction of user accounts and data, are produced and made available to consumers.IDG-PRC-010 (supports)
ISM-2074A general-purpose AI usage policy is developed, implemented and maintained.IDG-CON-007 (partial), IDG-TEC-017 (supports)
ISM-2112AI applications that process classified data have their ability to directly access external public data sources disabled.IDG-TEC-017 (supports)
ISM-2151Backups are stored using a technically enforced immutability mechanism that prevents their modification or deletion for the duration of their retention period.Deliberate CARE departure (see IDG-TEC-007)
Appendix D · Complete Master Index

Master Control Register & Lifecycle Index

All 68 proposed IDG controls with lifecycle stage, CARE, FAIR and ISM mappings
Control IDTitleLifecycle StageAudienceCAREFAIRISMEvidence
IDG-ASR-001 Regular CARE and FAIR maturity self-assessment with community review Stage 8: Measure & Assure both A2 R1 E2 - - Automated
IDG-ASR-002 Continuous automated control evidence anchored to the audit chain Stage 8: Measure & Assure both A2 R1 - - Automated
IDG-ASR-003 Community data inventory and FAIR metadata quality verification Stage 8: Measure & Assure both A2 C2 R1 F2 R1 R1.2 - Automated
IDG-ASR-004 Periodic verification of data transfer logs and backup restoration drills Stage 8: Measure & Assure both E1 A3 - ISM-1294 ISM-1515 Manual
IDG-ASR-005 Independent partnership and governance health check Stage 8: Measure & Assure both R1 E2 C3 - - Manual
IDG-CON-001 A named accountable officer Stage 5: Access, Use & AI consumer R1 A3 - - Manual
IDG-CON-002 Only approved users Stage 5: Access, Use & AI consumer A3 E1 - ISM-0405 Manual
IDG-CON-003 A secure environment matched to the data Stage 4: Store & Protect consumer E1 - ISM-1080 Manual
IDG-CON-004 Use only for the agreed purpose Stage 5: Access, Use & AI consumer A3 E1 - - Manual
IDG-CON-005 No onward sharing Stage 6: Share & Publish consumer A3 R1 - - Manual
IDG-CON-006 No re-identification and no unapproved linkage Stage 6: Share & Publish consumer E1 E2 - - Manual
IDG-CON-007 No AI training or processing without agreement Stage 5: Access, Use & AI consumer A3 E3 - ISM-2074 Manual
IDG-CON-008 Tell the community about any breach Stage 7: Retain, Return & Destroy consumer R1 E1 - ISM-1880 Manual
IDG-CON-009 Destroy or return the data at the end, and attest to it Stage 7: Retain, Return & Destroy consumer A1 R1 - - Manual
IDG-CON-010 Community review before publication Stage 6: Share & Publish consumer A3 E1 R3 - - Manual
IDG-CON-011 Benefit sharing and attribution Stage 6: Share & Publish consumer C1 C3 R2 - - Manual
IDG-CON-012 Recipient staff are trained before data is released Stage 5: Access, Use & AI consumer R1 E1 - ISM-0252 Manual
IDG-CON-013 Access records available to the community Stage 8: Measure & Assure consumer A2 R1 - ISM-1988 Manual
IDG-GOV-001 Community authority over Indigenous data Stage 1: Plan & Govern both A1 A3 - - Automated
IDG-GOV-002 Operator roles cannot override community authority Stage 5: Access, Use & AI both A3 E1 - ISM-1611 ISM-1613 ISM-1508 ISM-1610 Automated
IDG-GOV-003 Right to decline and to withdraw Stage 2: Collect & Consent both A1 E3 - - Code
IDG-GOV-004 Governing body oversight below community authority Stage 1: Plan & Govern both R1 A3 - - Manual
IDG-GOV-005 Aboriginal and Torres Strait Islander people in data governance Stage 1: Plan & Govern both E2 A3 - - Manual
IDG-PPL-001 Defined roles and separation of duties Stage 1: Plan & Govern both A3 R1 - - Automated
IDG-PPL-002 Custodian appointments and revocations come from the community Stage 1: Plan & Govern both A1 A3 - - Automated
IDG-PPL-003 Cultural competency and data sovereignty training before access Stage 5: Access, Use & AI consumer R1 E1 - ISM-0252 Manual
IDG-PPL-004 Vetting and suitability Stage 5: Access, Use & AI consumer E1 - ISM-0434 Manual
IDG-PPL-005 Key custodians Stage 4: Store & Protect both A1 A3 - ISM-0507 Automated
IDG-PPL-006 Strong authentication for privileged and custodian roles Stage 5: Access, Use & AI both E1 - ISM-1173 ISM-1682 ISM-1504 Automated
IDG-PPL-007 Joiners get the least access they need, once approved Stage 5: Access, Use & AI consumer A3 E1 - ISM-0405 ISM-1852 ISM-1508 Automated
IDG-PPL-008 Movers have their access reviewed Stage 5: Access, Use & AI both E1 - - Automated
IDG-PPL-009 Leavers and project ends remove access promptly Stage 5: Access, Use & AI both A3 E1 - ISM-0430 ISM-1845 ISM-1404 ISM-1648 Automated
IDG-PPL-010 Independent audit of access, visible to the community Stage 8: Measure & Assure both A2 R1 - ISM-1815 ISM-0414 Automated
IDG-PPL-011 Outside parties have time-limited, purpose-limited access Stage 5: Access, Use & AI both A3 E1 - ISM-0441 Automated
IDG-PPL-012 Support for community data capability, on the community's terms Stage 1: Plan & Govern both R2 C1 - - Manual
IDG-PRC-001 Data sharing agreements with required clauses Stage 6: Share & Publish both A1 A3 C3 R1.1 ISM-0072 Automated
IDG-PRC-002 Free, prior and informed consent before collection Stage 2: Collect & Consent both A1 E1 - - Automated
IDG-PRC-003 Purpose limitation Stage 5: Access, Use & AI both A3 E1 - - Automated
IDG-PRC-004 Approval for secondary use and derived data Stage 5: Access, Use & AI both A3 C3 E3 R1.1 - Automated
IDG-PRC-005 Consent variation and withdrawal Stage 2: Collect & Consent both A1 A3 - - Automated
IDG-PRC-006 Suspension when new information comes to light Stage 2: Collect & Consent both E1 A3 - - Automated
IDG-PRC-007 Periodic access review by the custodian group Stage 5: Access, Use & AI both A3 R1 - ISM-1647 Automated
IDG-PRC-008 Agreement review and expiry Stage 6: Share & Publish both A3 R1 - - Automated
IDG-PRC-009 Incident and breach notification to the community Stage 7: Retain, Return & Destroy both R1 E1 E2 - ISM-1880 ISM-0133 ISM-0142 Manual
IDG-PRC-010 Destruction and attestation of destruction Stage 7: Retain, Return & Destroy both A1 R1 - ISM-0313 ISM-0348 ISM-0363 ISM-1735 ISM-2053 Automated
IDG-PRC-011 Onward sharing is controlled by the sharing organisation Stage 6: Share & Publish both A3 R1 - - Manual
IDG-PRC-012 Re-identification risk is controlled before release Stage 6: Share & Publish both E1 E2 - - Manual
IDG-PRC-013 Return of data to the community Stage 7: Retain, Return & Destroy community A2 C3 - ISM-1574 Automated
IDG-PRC-014 Community data priorities Stage 1: Plan & Govern both A2 C1 - - Manual
IDG-PRC-015 Disaggregated data for the community on request Stage 5: Access, Use & AI both A2 C2 - - Manual
IDG-PRC-016 Data stewardship and data quality reviewed with the community Stage 2: Collect & Consent both E1 E3 A3 R1.2 - Manual
IDG-TEC-001 Every record carries a classification that can only be raised automatically Stage 3: Classify & Label both A3 E1 R1 ISM-0393 Automated
IDG-TEC-002 Cultural protocols and Local Contexts labels travel with the data Stage 3: Classify & Label both A3 R3 R1.1 R1.3 - Automated
IDG-TEC-003 Existence of restricted records fails closed Stage 3: Classify & Label both E1 A3 - - Automated
IDG-TEC-004 Encryption at rest for sensitive Indigenous data Stage 4: Store & Protect both E1 - ISM-1080 ISM-1059 ISM-1811 Automated
IDG-TEC-005 Encryption in transit Stage 4: Store & Protect both E1 - ISM-1139 ISM-1781 ISM-1277 Automated
IDG-TEC-006 Key custody options up to community-held keys Stage 4: Store & Protect both A1 A3 - ISM-0507 Automated
IDG-TEC-007 Cryptographic erasure per custodian group Stage 7: Retain, Return & Destroy both A1 E3 - - Automated
IDG-TEC-008 Access control that operator roles cannot override Stage 5: Access, Use & AI both A3 A1.2 ISM-1268 Automated
IDG-TEC-009 Tenant isolation enforced by the database Stage 4: Store & Protect both E1 A3 A1.2 ISM-1268 Automated
IDG-TEC-010 Tamper-evident audit log Stage 8: Measure & Assure both R1 A2 R1.2 ISM-1815 ISM-1988 ISM-1405 ISM-1985 ISM-0988 ISM-1989 Automated
IDG-TEC-011 Communities can verify the audit record independently Stage 8: Measure & Assure community A2 R1 - - Automated
IDG-TEC-012 Data residency onshore by default Stage 4: Store & Protect both A3 E1 - ISM-1572 Automated
IDG-TEC-013 Sub-processors are disclosed Stage 4: Store & Protect both R1 A3 - ISM-1637 ISM-1572 Manual
IDG-TEC-014 Exports only under an agreement, with protocols attached Stage 6: Share & Publish both A3 R1 R1.1 R1.2 ISM-0663 ISM-0661 ISM-1187 ISM-1586 Automated
IDG-TEC-015 Presentation controls on display and export Stage 6: Share & Publish both E1 R3 - - Automated
IDG-TEC-016 Retention limits and verified purge, including backups Stage 7: Retain, Return & Destroy both E1 E3 - ISM-1511 ISM-1547 Automated
IDG-TEC-017 AI and model training restrictions Stage 5: Access, Use & AI both A3 E3 - ISM-2074 ISM-2112 Automated