docs(readme): add Security & Compliance posture section#122
Merged
Conversation
Document HAIP's built-in security posture (tenant isolation in depth, layered auth, Connect/OTA authentication, input/transport hardening, fail-closed prod defaults) alongside the existing PCI/GDPR/tax compliance table. Framed as design, not a disclosure. https://claude.ai/code/session_01Jq85xVJDW1NpvxQrnEdFdt
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Renames the README's "Compliance" section to Security & Compliance and documents HAIP's built-in security posture — tenant isolation in depth (guard + data layer + FK ownership), layered Keycloak + local RBAC, per-property Connect credentials, authenticated OTA webhooks, input/transport hardening (validation, CORS allowlist, security headers, SSRF protection, rate limiting), and the fail-closed production boot check.
Framed as design/posture, not a vulnerability disclosure. Keeps the existing PCI/GDPR/tax/auth rows. Adds an honest one-line note that security is ongoing and to pair with a deployment review + Keycloak
property_idsclaim before production.Docs-only.
🤖 Generated with Claude Code
Generated by Claude Code