Skip to content

Add CODEOWNERS with security-sensitive path owners (parity with IcebergCTI) #321

Description

@richardmhope

Parity gap: no CODEOWNERS (IcebergCTI has one)

Cross-repo parity review of the Iceberg family (IcebergCTI / IcebergTTX / IcebergEBS). This repo has no CODEOWNERS; the sibling IcebergCTI ships one that assigns review ownership, with explicit owners on security-sensitive paths so those changes always route to the right reviewer.

IcebergCTI baseline: .github/CODEOWNERS with a default owner plus explicit entries for the auth code, audit/SIEM services, /.github/, SECURITY.md, and the Dockerfile.

Current state (this repo): no CODEOWNERS at root, .github/, or docs/; require_code_owner_reviews is off in branch protection.

Acceptance criteria

  • Add .github/CODEOWNERS with a default owner (an @IcebergAI team, not a personal handle) and explicit owners for security-sensitive paths (auth, any audit/security services, .github/, SECURITY.md, Dockerfile, deploy manifests).
  • Consider enabling require_code_owner_reviews on main once the file is in place.

Reverse-parity: adopting a practice IcebergCTI already has. (Note: IcebergCTI's own CODEOWNERS still uses a personal handle — see its issue #154 — so use an org team here from the start.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    parityGap vs the IcebergTTX (deep_thought) house standardtech-debtMaintainability, dead code, smells

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions