IF Commons GitHub

Pentest: the passive checks

0003Active

0003-pentest-passive · owner if · domain commons

Requirements

FR-001checkpassing

The passive checks MUST be data in the shape the tenant keeps a saved check in: an identity, a question in words, one statement of SQL that selects what is wrong (an empty answer passes) and the controls of NIST SP 800-53 it is evidence for; each statement MUST read only the relations of the estate (endpoint, attribute, link, service, asset and clock).

Enforced (check): .github: cd commons/pentest && bun run verify — suite/passive.test.ts

Proved by: pentest/suite/passive.test.ts

Written in: pentest/src/governance/passive.ts

Tests: passed: suite/passive.test.ts the checks are data in the shape of a saved check, with controls of SP 800-53, and each st

FR-002checkpassing

Each check MUST find what it says over an estate that has it and find nothing over one that does not: an endpoint in the clear open to the internet, a management, orchestration, data, file or directory service open to the internet, an API open to the internet with no authentication, an endpoint over TLS with no certificate, a certificate that ends within thirty days or has a weak key, a mobile app that allows cleartext, and an endpoint in the clear that a mobile app calls.

Enforced (check): .github: cd commons/pentest && bun run verify — suite/passive.test.ts

Proved by: pentest/suite/passive.test.ts

Written in: pentest/src/governance/passive.ts

Tests: passed: suite/passive.test.ts each check names what is wrong in an estate that has it, and every check passes in one tha

Acceptance scenarios

  1. Given an estate with a database endpoint open to the internet, When the data check runs, Then it names the endpoint, per FR-002.
  2. Given a clean estate, When every check runs, Then each passes, per FR-002.

Out of scope

Edge cases

  • A check says nothing of a service nobody described: it is as good as what the estate holds, per FR-001.

Assumptions

Open questions

  • None.

Key entities

  • Passive check.

Success criteria

SC-001success criterion

The tests of the library pass, with every check run over an estate by the engine of the estate query.

Review & acceptance checklist

  • [x] Every requirement is testable (MUST / MUST NOT), not aspirational
  • [x] No company fact is asserted here
  • [x] Every open item is marked, not silently decided

Titles, headings, exports, tables, columns and requirements. Esc closes.