CDP 35948467: Application ID (app/AI) #2
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
CDP Control ID:
35948467Category: User Access Management
Frequency: Annually
Owner: h.noerenberg
Parent: #1
Requirement & Guidance
User Access Management Requirement: If an Application ID is required, each Application should be assigned a unique Application ID. Individual users, including System Administrator, must not use Application IDs to access systems. (i.e. where available disable/revoke the regular user login capability on generic IDs and consider the use of surrogacy permissions, SSH keys, etc.) Guidance: Confirm that applications IDs, when assigned to resources, are unique to the application. Application Ids are generally default id's generated by the application (e.g.: sys, oracle ids from Oracle, SA in SQL). Confirm these applications IDs are not used for accessing systems like normal User Ids.Additional information can be found on CDP website User Access Management
CapaKraken Action Plan — 35948467 Application ID
Scope: Eindeutige Application IDs / Service Accounts (nicht Individual-User).
Aktueller Stand (aus
docs/acn-security-compliance-status.md):Todos:
capakraken, Redis, SMTP-User, Sentry-DSN, ggf. Azure/OpenAI-Keys)pg_hba.confrestriktiv)docs/application-ids-inventory.md(neu)Nachweis/Kontext:
docs/security-architecture.mdSek. 12 (DB Security).env.example— Key-Inventar als AusgangspunktCapaKraken Compliance-Status
EAPPS-Mapping:
3.2.2.1.01 / 3.2.2.1.04Status: ✅ OK (laut
docs/acn-security-compliance-status.md)Zusammenfassung
CapaKraken ist eine interne Web-App; es existieren keine geteilten Application IDs oder Service-Accounts auf DB-/Auth-Ebene. Jeder User hat eine eindeutige ID.
Nachweis
User.email @unique—packages/db/prisma/schema.prismaapps/web/src/server/auth.tsCRON_SECRETHeader (nicht User-Login) —apps/web/src/lib/cron-auth.tsdocs/acn-security-compliance-status.md— EAPPS 3.2.2.1.01 = OKEntscheidung: Control ist nachweislich erfüllt → Ticket wird geschlossen.