# IDG self-assessment template. Generated by pnpm idg:build; copy it before filling it in.
# See docs/idg/self-assessment.md. A self-assessment is not certification.
format: blaksmith.idg-assessment/v1
catalogue_version: "0.1"
organisation: ""
scope: ""
levels_held: []
assessed_on: ""
controls:
  - id: IDG-ASR-001
    version: 1
    title: Regular CARE and FAIR maturity self-assessment with community review
    domain: ASR
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The 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.
      ml2: Each 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.
      ml3: Reassessment 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.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-ASR-002
    version: 1
    title: Continuous automated control evidence anchored to the audit chain
    domain: ASR
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Automated checks exist for core technical controls and are run before releases, with results retained alongside the commit tested.
      ml2: Every 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.
      ml3: Evidence 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.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-ASR-003
    version: 1
    title: Community data inventory and FAIR metadata quality verification
    domain: ASR
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The 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.
      ml2: Inventories are generated from live system metadata with provenance, protocols, consent, agreements and outside-party access included, and are verified for completeness at least annually.
      ml3: Communities 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.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-ASR-004
    version: 1
    title: Periodic verification of data transfer logs and backup restoration drills
    domain: ASR
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Transfer and export logs are sampled and checked against active agreements at least quarterly, and a written backup restoration procedure includes reapplying erasures and purges.
      ml2: Transfer 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.
      ml3: Automated 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.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-ASR-005
    version: 1
    title: Independent partnership and governance health check
    domain: ASR
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The organisation and community agree terms for periodic review of their data governance relationship and document any concerns raised.
      ml2: An 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.
      ml3: Independent 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.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-CON-001
    version: 2
    title: A named accountable officer
    domain: CON
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: An accountable officer is named in the agreement, with contact details the community holds.
      ml2: The accountable officer signs the agreement and every attestation, and a replacement is named before they leave.
      ml3: The accountable officer reports to the community at agreed intervals on how the data is being used.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-CON-002
    version: 1
    title: Only approved users
    domain: CON
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: A list of people with access is kept and given to the community.
      ml2: Each person is approved before access, and the list is reviewed at least every six months.
      ml3: Access is technically limited to the approved list, and changes are notified to the community.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-CON-003
    version: 1
    title: A secure environment matched to the data
    domain: CON
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The environment where the data will be held is described in the agreement.
      ml2: The environment has access control, encryption at rest, logging and backups, with no personal device or unapproved cloud use, confirmed before data is released.
      ml3: The environment has been independently assessed, and the data cannot be copied out of it without approval.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-CON-004
    version: 1
    title: Use only for the agreed purpose
    domain: CON
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Everyone with access knows the agreed purpose and has agreed in writing to keep to it.
      ml2: New uses are put to the community for approval before work starts, and the decision is recorded.
      ml3: Use of the data is logged against the agreed purpose, and the log is available to the community.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-CON-005
    version: 1
    title: No onward sharing
    domain: CON
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Staff and contractors have agreed in writing not to share the data onward.
      ml2: Any onward share has the community's written approval and is recorded.
      ml3: Technical controls prevent the data being sent outside the approved environment.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-CON-006
    version: 2
    title: No re-identification and no unapproved linkage
    domain: CON
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Everyone with access has agreed in writing not to re-identify or link the data.
      ml2: Approved linkages are recorded with the community's approval, and accidental identification is reported.
      ml3: Outputs are checked for re-identification risk before they leave the environment.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-CON-007
    version: 1
    title: No AI training or processing without agreement
    domain: CON
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Everyone with access has agreed in writing not to use the data with AI tools unless the agreement allows it.
      ml2: AI tools are blocked or restricted in the environment where the data is held.
      ml3: Any permitted AI use is limited to tools and locations the community approved, and is logged.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-CON-008
    version: 1
    title: Tell the community about any breach
    domain: CON
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The organisation's incident procedure includes notifying the community and the custodian.
      ml2: Notification times are set in the agreement and tested in an exercise.
      ml3: The community is involved in investigating and reviewing every incident involving its data.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-CON-009
    version: 1
    title: Destroy or return the data at the end, and attest to it
    domain: CON
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The organisation knows where every copy of the data is held.
      ml2: At the end, every copy, backup and derived file is destroyed or returned and the accountable officer signs an attestation.
      ml3: Destruction is independently verified or evidenced by system records, and the attestation is given to the community.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-CON-010
    version: 2
    title: Community review before publication
    domain: CON
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The agreement says which outputs the community reviews and how long it has.
      ml2: Every output is sent for review before release, and the community's response is recorded.
      ml3: The community is involved in interpreting the findings, not only reviewing them.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-CON-011
    version: 1
    title: Benefit sharing and attribution
    domain: CON
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Benefits and attribution are written into the agreement.
      ml2: Benefits delivered and findings shared are recorded and reported to the community.
      ml3: The community helps decide what benefit means for each project, and reviews whether it was delivered.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-CON-012
    version: 1
    title: Recipient staff are trained before data is released
    domain: CON
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Approved users complete training before access.
      ml2: Training records are kept and provided to the community on request, and refreshed at least every 12 months.
      ml3: Training is designed or delivered with the community or an Indigenous-led provider.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-CON-013
    version: 2
    title: Access records available to the community
    domain: CON
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Access to the data is logged.
      ml2: Access logs are kept for the life of the agreement and provided on request.
      ml3: Access logs are reported to the community at agreed intervals without being asked.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-GOV-001
    version: 5
    title: Community authority over Indigenous data
    domain: GOV
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The organisation keeps a register of which communities its Indigenous data relates to and who each community has nominated to decide about it.
      ml2: Every decision to collect, use, share or destroy Indigenous data has a recorded approval from the community's nominated people before it takes effect.
      ml3: Systems refuse an action that has no current community approval, and the community can review every decision made under its authority.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-GOV-002
    version: 3
    title: Operator roles cannot override community authority
    domain: GOV
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Policy states that no operator role or emergency access process grants access to protocol-bound data.
      ml2: Access controls enforce the policy, and each use of emergency access on other data is logged and reviewed after the event.
      ml3: The 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.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-GOV-003
    version: 1
    title: Right to decline and to withdraw
    domain: GOV
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Agreements state the right to decline and to withdraw, and the community has been told how to use it.
      ml2: A withdrawal stops new use within an agreed time, and the organisation records what was stopped, returned or destroyed.
      ml3: Systems stop use as soon as a withdrawal is recorded, and the return or destruction terms cover derived data and copies held by others.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-GOV-004
    version: 2
    title: Governing body oversight below community authority
    domain: GOV
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The 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.
      ml2: The 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.
      ml3: The 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.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-GOV-005
    version: 1
    title: Aboriginal and Torres Strait Islander people in data governance
    domain: GOV
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The organisation names a lead for its governance of Indigenous data and records which of its bodies make or advise on decisions about that data.
      ml2: Those bodies include Aboriginal and Torres Strait Islander members whose views are recorded. Members from outside the organisation are paid for their time.
      ml3: Aboriginal 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.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PPL-001
    version: 1
    title: Defined roles and separation of duties
    domain: PPL
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The roles are written down, each with its duties, and the people in each role are known.
      ml2: Conflicting roles are kept apart, and any exception is approved, recorded and reviewed.
      ml3: Systems enforce the separation, and the community can see who holds each role for its data.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PPL-002
    version: 1
    title: Custodian appointments and revocations come from the community
    domain: PPL
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Each appointment and revocation in the register kept under IDG-GOV-001 is traceable to an instruction from the community.
      ml2: Appointments and revocations take effect only on a recorded instruction from the community, and revocations take effect the same day.
      ml3: The community, through people it chooses, makes appointments and revocations directly in the system, and the organisation cannot change them on its own.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PPL-003
    version: 2
    title: Cultural competency and data sovereignty training before access
    domain: PPL
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Training exists, and people complete it before they get access to Indigenous data.
      ml2: Completion and refresh dates are recorded, and access is removed when training lapses.
      ml3: Training 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.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PPL-004
    version: 1
    title: Vetting and suitability
    domain: PPL
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The organisation's existing personnel checks are applied to everyone with access to Indigenous data at these levels.
      ml2: Checks are repeated on a set cycle, and any community requirements are recorded and met before access is given.
      ml3: Access is tied to current suitability, so it is suspended automatically when a check lapses or is failed.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PPL-005
    version: 1
    title: Key custodians
    domain: PPL
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Key custodians are named, and key actions are limited to them by policy.
      ml2: Key actions need multi-factor authentication and a recorded reference and reason, and every action is logged.
      ml3: Key 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.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PPL-006
    version: 1
    title: Strong authentication for privileged and custodian roles
    domain: PPL
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Multi-factor authentication is required for administrative and custodian accounts.
      ml2: Sensitive actions need authentication within the last few minutes, and API keys cannot perform them.
      ml3: Phishing-resistant methods such as passkeys are required, and remembered devices cannot skip them.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PPL-007
    version: 2
    title: Joiners get the least access they need, once approved
    domain: PPL
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Access requests are approved by a named person and recorded.
      ml2: Access is granted only after training, checks and signed conditions are recorded, and starts at the least privileged role.
      ml3: Provisioning is automated from an approved source, and access to each community's data needs that community's appointment.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PPL-008
    version: 1
    title: Movers have their access reviewed
    domain: PPL
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Role changes trigger a manual access review, and the outcome is recorded.
      ml2: Access is adjusted on the day of the change, and existing sessions are ended.
      ml3: Role changes flow from an authoritative source, access is re-derived automatically, and a periodic review catches anything missed.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PPL-009
    version: 2
    title: Leavers and project ends remove access promptly
    domain: PPL
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: A leaver checklist covers every kind of access and every copy, and is completed for each leaver and project end.
      ml2: Access is removed on the last day, and the removal is recorded and checked.
      ml3: Removal is automatic from an authoritative source, including sessions and API keys, and the community is told when someone with access to its data leaves.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PPL-010
    version: 5
    title: Independent audit of access, visible to the community
    domain: PPL
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Access logs are kept and reviewed by someone other than the platform operators at least once a year.
      ml2: The review is at least quarterly, and the community receives a report of access to its data.
      ml3: The community can see access to its data at any time, from a log that cannot be changed without detection.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PPL-011
    version: 2
    title: Outside parties have time-limited, purpose-limited access
    domain: PPL
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Each outside party's access has a sponsor, a purpose and an end date on record.
      ml2: Access 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.
      ml3: The community approves each outside party's access to its data, and is told when it starts and ends.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PPL-012
    version: 1
    title: Support for community data capability, on the community's terms
    domain: PPL
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The organisation asks each community it holds data about whether it wants data capability support, and records the answer.
      ml2: Support a community asks for is planned with it, paid for and delivered, and the community reviews whether it met its needs.
      ml3: Support 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.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-001
    version: 3
    title: Data sharing agreements with required clauses
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: A written agreement with every required clause exists before any data is shared.
      ml2: Agreements are signed off by the community's custodians, kept in a register, and the systems that share data check an agreement is in place.
      ml3: Systems enforce each clause, so data outside the scope, formats, dates or purposes of an active agreement cannot be shared.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-002
    version: 2
    title: Free, prior and informed consent before collection
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Consent is obtained and recorded before collection, with who gave it, for what purpose and on what date.
      ml2: Systems refuse to ingest data that needs collective consent unless a consent record is supplied with it.
      ml3: Systems check the consent record against the community's own register before ingest, and keep it with the data.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-003
    version: 2
    title: Purpose limitation
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Agreed purposes are written down, and staff are told not to use data for anything else.
      ml2: Systems require a stated purpose for access at these levels and refuse purposes outside the agreement.
      ml3: Stated purposes are checked against the person's role and agreement, and the community can see which purposes were used.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-004
    version: 3
    title: Approval for secondary use and derived data
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Secondary uses and derived outputs are listed and approved by the community before use.
      ml2: Derived records are created without consent and cannot be used until the community grants it.
      ml3: Derived outputs are tracked back to their sources, and the community reviews each one with any benefit it produces.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-005
    version: 1
    title: Consent variation and withdrawal
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Variations and withdrawals are accepted in writing and recorded.
      ml2: Systems apply a narrowing or withdrawal at once, and refuse to treat a broadening as anything but a new grant.
      ml3: The community makes variations and withdrawals directly, and can see their effect on every dataset and recipient.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-006
    version: 1
    title: Suspension when new information comes to light
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Staff know to stop and report when they learn something that could change the community's decision.
      ml2: Raising new information suspends the affected consent in the system and records who raised it and what was learned.
      ml3: The community and any statutory recipient are notified automatically, and use resumes only on a fresh grant.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-007
    version: 1
    title: Periodic access review by the custodian group
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: A list of everyone with access to each community's data is given to its custodians each year.
      ml2: Custodians confirm or remove each person's access, and removals are carried out within an agreed time.
      ml3: Custodians run the review themselves in the system, and unconfirmed access is removed automatically.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-008
    version: 1
    title: Agreement review and expiry
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Each agreement has a review date and an end date in a register, and reviews are held.
      ml2: Reviews and expiries are raised automatically before they fall due.
      ml3: Expiry stops access automatically and starts the return or destruction process.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-009
    version: 2
    title: Incident and breach notification to the community
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: An incident procedure names the community contact for each dataset and the time for notifying them.
      ml2: Every incident affecting Indigenous data is recorded with when the community was told, and the procedure is tested.
      ml3: Detection feeds the community notification directly, and the community takes part in the review of each incident.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-010
    version: 3
    title: Destruction and attestation of destruction
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: A destruction procedure covers primary copies, backups, derived data and recipients' copies.
      ml2: Each destruction is attested by a named accountable person and the attestation is given to the community.
      ml3: Encryption 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.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-011
    version: 2
    title: Onward sharing is controlled by the sharing organisation
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Every agreement bans onward sharing unless the community approves it.
      ml2: Each approved onward share is recorded with the community's approval and the terms that bind the onward recipient.
      ml3: Exports are traceable to the recipient, so an unapproved onward copy can be identified.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-012
    version: 3
    title: Re-identification risk is controlled before release
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Every agreement bans re-identification and unapproved linkage.
      ml2: Data is released at the least detail the purpose needs, and approved linkages are recorded with the community's approval.
      ml3: Each release is assessed for re-identification risk before it leaves the organisation.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-013
    version: 3
    title: Return of data to the community
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Data is returned on request, in a format agreed with the community.
      ml2: Returned data carries its classification, protocols and agreements, and the return is recorded.
      ml3: The community can retrieve its data itself at any time, in open formats, with its protocols intact.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-014
    version: 1
    title: Community data priorities
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The organisation has asked each community it holds data about for its data priorities, and recorded them.
      ml2: Priorities are reviewed with the community at an interval it agrees, and the organisation reports what it has done on each.
      ml3: Community priorities shape what the organisation collects and analyses, and the community can point to decisions they changed.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-015
    version: 1
    title: Disaggregated data for the community on request
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The organisation can tell a community at what levels of detail it holds data about that community.
      ml2: Requests for disaggregated data are answered within a time agreed with the community, with reasons and alternatives for anything refused.
      ml3: The community can get data about itself at the levels it chooses without a separate request each time, under its own access rules.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-PRC-016
    version: 1
    title: Data stewardship and data quality reviewed with the community
    domain: PRC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Each set of Indigenous data has a named steward and a record of its source, how it was collected and its known limitations.
      ml2: The community can ask for errors to be corrected and context to be added. The organisation acts on each request and records what it did.
      ml3: Data 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.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-001
    version: 3
    title: Every record carries a classification that can only be raised automatically
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: A classification scheme exists and is applied to Indigenous data, with a recorded default.
      ml2: Systems store a classification on every record and take the strictest level when records are combined.
      ml3: Automated lowering is impossible, every change is recorded with who made it, and history reads at the current level.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-002
    version: 3
    title: Cultural protocols and Local Contexts labels travel with the data
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Protocols and labels are recorded against the records they apply to.
      ml2: Protocols that restrict access or use are enforced by the system, and labels are included in every export.
      ml3: Every label's meaning is enforced, labels are kept in sync with the community's own Local Contexts records, and derived records inherit them.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-003
    version: 2
    title: Existence of restricted records fails closed
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Restricted records are left out of the main search and listing screens for people without authority.
      ml2: Every read path, including search, counts, maps, exports and error messages, hides the record's existence.
      ml3: Hiding is tested automatically across every read path on each change.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-004
    version: 3
    title: Encryption at rest for sensitive Indigenous data
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Storage holding Indigenous data is encrypted at rest.
      ml2: Sensitive fields are encrypted by the application before they are stored, including in history and backups.
      ml3: All content, including names and derived search data, is encrypted, and a scheduled check proves no plaintext is stored.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-005
    version: 3
    title: Encryption in transit
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Public endpoints use TLS and redirect plain HTTP.
      ml2: Connections to databases, storage and between services are encrypted, and secure cookies are required.
      ml3: Every connection, including inside private networks, uses TLS with certificate verification, and weak protocols are refused.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-006
    version: 2
    title: Key custody options up to community-held keys
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Keys for Indigenous data are managed in a key management service, separate from the data.
      ml2: Each custodian group has its own key, and community keys are never escrowed by the operator.
      ml3: A community can hold its own key in its own account, and every use of it is visible to the community.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-007
    version: 3
    title: Cryptographic erasure per custodian group
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: A documented procedure can destroy a custodian group's key on the community's request.
      ml2: Erasure affects only that group's data, needs a recorded reference and reason, and is logged.
      ml3: Erasure is tested in a live drill, recorded in the tamper-evident audit log, and confirmed to the community.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-008
    version: 2
    title: Access control that operator roles cannot override
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Access to protocol-bound data is limited by configuration to authorised people.
      ml2: A single enforcement point checks custodian authority on every read, and refuses administrators, service accounts and AI agents without it.
      ml3: The refusal is tested automatically on every change, including for emergency access and every API surface.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-009
    version: 2
    title: Tenant isolation enforced by the database
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Tenant data is separated by application checks on every query.
      ml2: Database row-level security restricts every tenant table, and the application connects with a role that is subject to it.
      ml3: Isolation is verified automatically against a live database on every change, and no routine process runs with a role that bypasses it.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-010
    version: 3
    title: Tamper-evident audit log
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Access and changes are logged and the log is protected from routine editing.
      ml2: The log is hash-chained so changes are detectable, and the application cannot update or delete entries.
      ml3: The chain is verified on a schedule and its head is anchored outside the operator's control.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-011
    version: 2
    title: Communities can verify the audit record independently
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The community can ask for and receive the access record for its data.
      ml2: Access reports and digests of the audit log are published to the community on a schedule.
      ml3: The community can verify an export of the log against an anchored digest with its own tools.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-012
    version: 1
    title: Data residency onshore by default
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: The hosting region is documented and agreed with the community.
      ml2: Infrastructure fails to deploy outside the agreed regions, including backups and keys.
      ml3: Every service that processes the data, including AI and support tools, is checked against the agreed jurisdiction before use.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-013
    version: 2
    title: Sub-processors are disclosed
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: A current list of sub-processors, their locations and their access is available to the community.
      ml2: The community is told before a sub-processor is added or changed, and can object.
      ml3: The community's agreement is needed before a new sub-processor can handle its data.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-014
    version: 3
    title: Exports only under an agreement, with protocols attached
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Exports of Indigenous data are approved and recorded.
      ml2: Exports carry classification, protocols and agreements, refuse material that would lose its protocols, and are watermarked for outside parties.
      ml3: The system refuses any export not covered by an active agreement for that recipient, scope and format.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-015
    version: 1
    title: Presentation controls on display and export
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Staff follow written rules for showing locations, deceased persons and warnings.
      ml2: The system applies generalisation, suppression, warnings and attribution on display.
      ml3: The same controls apply to every export and API, at a level of detail the community sets.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-016
    version: 3
    title: Retention limits and verified purge, including backups
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: A retention schedule covers each kind of Indigenous data and its backups.
      ml2: A scheduled process purges data at the end of its retention period, and backups expire within a stated time.
      ml3: Each purge is recorded in the tamper-evident log, verified, and reapplied after any restore from backup.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
  - id: IDG-TEC-017
    version: 1
    title: AI and model training restrictions
    domain: TEC
    maturity:
      ml0: Not in place, or not at ML1.
      ml1: Policy prohibits AI training on, or AI processing of, Indigenous data without agreement.
      ml2: Systems refuse to send restricted material to external AI services and leave it out of embeddings.
      ml3: Every AI feature, local or external, checks the agreement and consent before use, and the community can see where AI was used.
    applicable: true
    achieved: 0
    evidence: ""
    not_applicable_reason: ""
    notes: ""
attestation:
  accountable_officer: ""
  role: ""
  signed_on: ""
  statement: I am the accountable officer for the systems and data in scope. To the best of my knowledge, the levels recorded here are accurate and supported by the evidence listed. I understand that this is a self-assessment against a provisional, operator-drafted catalogue, and that it is not a certification or an endorsement by any community.
community_review:
  status: not_started
  reviewed_on: ""
  reference: ""
  notes: ""
