How PHALANX protects your data, your deployments, and the infrastructure that makes PHALANX operate.
PHALANX is designed on zero-trust, defense-in-depth principles. Every component assumes breach; every communication is intended to be authenticated and encrypted.
Local data is encrypted at rest using SQLCipher (AES-256, WAL mode). Network communication uses TLS in transit. Key management practices are being formalized as the platform matures.
Role-based access control and credential handling are part of the core architecture. Formal identity/MFA policy for hosted services will be published as those services go live.
LYNX's detection engine is built to eventually monitor PHALANX's own infrastructure, following the same architecture it provides to deployments — this is a roadmap item, not yet in production.
Infrastructure logging and monitoring practices are being defined alongside the platform's build-out. Details will be published here once operational.
A formal incident response plan is in development. Until published, security concerns should be reported directly — see Responsible Disclosure below.
Formal business continuity and disaster recovery targets (RTO/RPO) will be defined and published once PHALANX moves from development into hosted production use.