This document is a working template and must be reviewed by legal counsel for the applicable jurisdiction, actual service architecture and data-processing practices before launch.
1. Protected transport
Connections between devices and network infrastructure are designed around protected transport. Protocols and algorithms depend on the configuration and are confirmed in project documentation.
2. Infrastructure separation
Customer environments can use separate compute instances, individual network parameters, a public IP and a dedicated domain model. Boundaries are defined before launch.
3. Access management
Connection issuance, change and revocation processes are defined during deployment. Access should be provided only to required employees and devices.
4. Monitoring and incidents
Operational monitoring, logging and incident response depend on the selected configuration and are agreed with the customer. FAST2 does not claim unverified guarantees or certifications.
5. Responsible disclosure
Potential vulnerabilities may be reported to [SECURITY_EMAIL] after that address has been created and verified. Do not expose confidential data or disrupt the service while researching.