You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add systemd validation check to ValidateInstanceImage
- Add Check 4 to verify systemd is running or degraded
- Update SECURITY.md to document systemd requirement
- Update README.md Platform Support section
- Refactor ValidateInstanceImage into smaller helper functions to fix lint
- Validation tests automatically include new check
Co-Authored-By: Alec Fong <alecsanf@usc.edu>
Copy file name to clipboardExpand all lines: docs/SECURITY.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@ This document outlines the security requirements and best practices for implemen
16
16
**Implementation Requirements:**
17
17
18
18
- SSH server (OpenSSH or equivalent) must be installed and running on all instances
19
+
- systemd must be running and accessible via systemctl command
19
20
- SSH key pairs must be supported for authentication
20
21
- Public keys must be injectable during instance provisioning
21
22
- SSH access must be available through the configured firewall rules
@@ -136,4 +137,4 @@ For security issues, vulnerabilities, or questions:
136
137
137
138
---
138
139
139
-
**Note**: This document is a living document and will be updated as security requirements evolve. All cloud integrations must comply with these requirements to ensure the security and integrity of the Brev Compute SDK ecosystem.
140
+
**Note**: This document is a living document and will be updated as security requirements evolve. All cloud integrations must comply with these requirements to ensure the security and integrity of the Brev Compute SDK ecosystem.
0 commit comments