KamoCRM

Persist SecurityService PHI access trail to phi_access_log

FeatureSecurityService
Shipped
3 ஆகஸ்ட், 2026 அன்று 3:09 PM UTC
Author
Kamo
Commit
b0ef82f

The §164.312(b) trail was going to Slf4jPhiAccessLogWriter: 14-day platform retention against a six-year obligation, and nothing that can be queried. The lead reads and CSV/HMDA exports this service records are the accesses a §164.528 accounting is assembled from, so the trail has to survive in a table. Swaps in JpaPhiAccessLogWriter via a bean PhiAccessRecorder picks up through ObjectProvider.getIfUnique — no call site in PhiAccessAuditor changes. The matching com.kamo.z.shared.phi.audit entry in @EnableJpaRepositories ships in this same commit: the bean cannot be constructed without the repository, and declaring one without the other is what CrashLooped login earlier today.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing