Wrote a scope rule after a credential leak
Wrote a scope rule into the repository after a restructure carried
another company's inventory, firewall allowances and prose into it —
and kept the quarantined residue under the secret scanner rather
than excluding it.
September 2026

Situation. Work done for a different company rode along through a
repository restructure and stayed. What came with it was not
abstract: a scratch log holding live plaintext credentials, which
sat in the tree past every guard for most of the repository's
history; a stale inventory naming that company's host; and a
firewall task file opening ports to sixteen of its client networks.
None of it ran. That is exactly why it survived — nothing that runs
nowhere is ever reviewed again.

Task. The boundary had to become a rule with a test attached, rather
than an intention, and the residue had to be dealt with in a way
that did not simply hide it.

Action. The rule is now the opening section of the repository's
instruction set: this repository manages one company's
infrastructure and only that, and another party's host, inventory,
firewall allowance, DNS zone or credential does not belong in it —
not even disabled, commented out, or parked in a file no playbook
imports. The practical test is written next to it: would this
company still be responsible for this if the relationship ended. The
residue was quarantined into a clearly‑named directory rather than
deleted, so the history stays legible, and the quarantine is
deliberately partial — the two structural linters skip it, and the
secret scanner, the vault guard and the emoji check deliberately
still read it, because those are the three that would catch the
thing that got in. The leak itself produced a linter rule: a custom
pattern that flags a credential passed as a command‑line flag, which
is the shape the leaked one had and which the standard rule set did
not match.

Result. The scope boundary is a written rule with a stated test, the
residue is visible rather than buried, and the specific shape of
credential that got through now fails a commit. The lesson recorded
alongside it is the general one: the dangerous artefact is not the
one that runs, it is the one that does not, because that is the one
nobody reads again.

Categories:
1Data Governance	/categories/data-governance/	data.engineer.company	70
1Infrastructure	/categories/infrastructure/	data.engineer.company	70
1Automation & CI/CD	/categories/automation/	data.engineer.company	70
1Security	/categories/security/	data.engineer.company	70
1Documentation	/categories/documentation/	data.engineer.company	70

Services:
1Data Governance & Quality	/services/data-governance/	data.engineer.company	70
1Security & Access Management	/services/security-access/	data.engineer.company	70
1AI Agent Security	/services/ai-security/	data.engineer.company	70
1Technical Documentation	/services/technical-documentation/	data.engineer.company	70

hThis page on the web	URL:https://data.engineer.company/portfolio/wrote-a-scope-rule-after-a-credential-leak/	data.engineer.company	70
