Encrypted vault controls
Create the encrypted vault
Cryptographic profile
- KDF
- PBKDF2 / SHA-256
- Iterations
- 310,000
- Cipher
- AES-GCM-256
- IV
- Random 12-byte per record
- AAD
- vault version + record type + record ID
- Key storage
- Memory only while unlocked
No-PII controls, import safeguards, audit design, and future member-persistence review.
Carry forward v155 security concepts as reusable services instead of UI-layer patches.
Preserved v155 / v154 capability lineage
The modular implementation preserves accepted legacy behavior while applying the current security, evidence-governance, and no-taxpayer-data boundaries.
Security Vault v165
Restored from the v153.2/v154 security model. Metadata-only real case records are encrypted locally with PBKDF2-SHA-256 at 310,000 iterations and AES-GCM-256. The decryption key exists only in browser memory after unlock.
Encrypted vault controls
Data classification
The public CPS architecture is synthetic/no-PII and has no taxpayer-data field model.
CPS_DATA_BOUNDARY.taxpayerDataAllowed === false
Authority
CPS does not perform, transmit, authorize, or represent official IRS account actions.
CPS_DATA_BOUNDARY.officialAccountActions === false
Integration
No live connection to IDRS or AMS is present in the modular public CPS stack.
liveIdrsConnection === false && liveAmsConnection === false
PII prevention
Ask CPS screens obvious TIN/SSN/EIN, email, phone, DOB-context, and bank/account-number patterns before evidence retrieval.
detectUnsafeAskPrompt()
Evidence governance
Review-gated, stale/unknown, superseded, or audience-restricted legacy material cannot become public procedural evidence.
v158 knowledge governance + v159 Ask CPS evidence eligibility
Persistence
Metadata-only real case tracker records may persist locally only inside the encrypted CPS vault. Scenario attempts remain browser-memory only.
PBKDF2-SHA-256 / 310000 + AES-GCM-256
Persistence
Authentication, authorization, encryption, audit, retention, privacy/security/records review, backup/restore, migrations, and independent PII/FTI validation are prerequisites.
v163 persistence prerequisites
Local safety scanner
The scanner runs in browser memory. Do not paste real taxpayer or protected information even for testing.
No obvious protected-data pattern detected. This does not authorize entry of real taxpayer data.