coulomb/security-canon
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Name access-engine as the only authorization decision point.

Browse source 
Assistant: grok
Assistant-Session: 01a0d25d-d358-7e13-b84a-d007fbb7e34f
This commit is contained in:
tegwick 2026-09-24 09:56:43 +02:00
parent 7e2de19dc6
commit 02f896555a
1 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

7
INTENT.md
View file

@ -34,9 +34,10 @@ depends:
- **NetKingdom** owns its security architecture, its standards of record,
including the security layer model, and any NetKingdom-specific profiles that
import this canon.
- **flex-auth** owns authorization decisions; **key-cape** and Keycloak own
login, OIDC, and MFA; **OpenBao** owns secret custody. SecurityCanon describes
those concepts; it does not perform them.
- **access-engine** (the repository is still `flex-auth`) owns authorization
decisions; **key-cape** and Keycloak own login, OIDC, and MFA; **OpenBao**
owns secret custody. SecurityCanon describes those concepts; it does not
perform them. There is one decision point.
- **whitehat-security** owns adversarial evidence and findings practice.
- **InfoTechCanon** remains the authority for the shared roots — artifact,
ownership, relationship, mapping, assimilation, profile, pattern, conformance,