Security
Security Overview
What can be safely said about security boundaries before final Security review.
English localization is preserved as a draft. It uses the same claim IDs and status model as the Russian source, but remains noindex until editorial review.
Public docs can only state verified boundaries: safe artifacts must not include keys or private payloads; validation jobs store sanitized results; operator-side lock can mark credentials as revoked. Exact internal storage, encryption and rotation mechanisms are not published.
This section requires Security review and is not included in the sitemap as a final page.
Safe To Publish
- High-level separation of public, personal and operator scopes.
- Requirement that public artifacts do not include secrets.
- User guidance to minimize API permissions.
Do Not Publish
- Secret names and private environment variables.
- Internal topology and host details.
- Exact credential storage mechanisms without review.