-
Notifications
You must be signed in to change notification settings - Fork 63
Add security documentation for credentials and deployment #2696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Create new security.md page documenting: - Security boundaries (Docker network, host, network configuration) - All backend credentials (Redis, MinIO, SERVICE_PASSWORD, SECRET_KEY_BASE) - users.acl file format and relationship to .env - Step-by-step instructions for changing passwords - Security recommendations for production deployments - Frontend vs backend authentication distinction - Update installation.md to link to new security documentation Closes #2538 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2696 +/- ##
==========================================
- Coverage 79.31% 79.24% -0.07%
==========================================
Files 662 664 +2
Lines 52588 52823 +235
Branches 734 734
==========================================
+ Hits 41708 41858 +150
- Misses 10800 10885 +85
Partials 80 80
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
clayandgen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I briefly mention using a dynamic secret manager in https://docs.openc3.com/docs/guides/scripting-api#initialize_offline_access, I'm curious if we'd like to add something about that here as well
|
|
||
| By default, COSMOS only listens on localhost (127.0.0.1). This configuration keeps COSMOS completely off the network and is only vulnerable to local users of the host computer. | ||
|
|
||
| For production use, it is recommended to open COSMOS to the network and run clients from other machines. This removes browser load from the host computer and allows better securing of the host. See [SSL/TLS](../configuration/ssl-tls) for configuring HTTPS. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe the network and clients should be a bit more specific here, this sentence isn't very intuitive to me
Summary
security.mdpage in the public documentation covering security boundaries, all backend credentials, users.acl file, and deployment security recommendationsinstallation.mdto link to the new security documentationCloses #2538
Closes https://github.com/OpenC3/cosmos-enterprise/issues/298
See OpenC3/cosmos-project#32
See https://github.com/OpenC3/cosmos-enterprise-project/pull/29
🤖 Generated with Claude Code