remediations
This commit is contained in:
@@ -134,14 +134,15 @@ As an operator, I want a checklist of potential missing configuration from exist
|
||||
- **FR-001**: The system MUST designate the new VPS as the primary host for reverse proxying and ensure all enabled services are routed through it without relocating the services.
|
||||
- **FR-002**: The system MUST ensure proxy configuration is enabled for all services currently enabled on the host server so traffic flows through the new VPS while services remain on the host server.
|
||||
- **FR-003**: The system MUST request existing proxy configuration files for verification and flag any subdomain mismatches against current service definitions.
|
||||
- **FR-004**: The system MUST apply firewall rules on the new VPS that match the existing VPS behavior for all documented inbound and outbound flows.
|
||||
- **FR-014**: The system MUST apply the existing iptables ruleset as-is to achieve firewall parity.
|
||||
- **FR-004**: The system MUST apply the existing iptables ruleset as-is on the new VPS to match the existing VPS behavior for all documented inbound and outbound flows.
|
||||
- **FR-005**: The system MUST enable the VPN configuration on the new VPS with the specified peer addresses and ensure each peer is uniquely identified.
|
||||
- **FR-006**: The system MUST support encrypting sensitive VPN keys and pause for user-provided secret material when required.
|
||||
- **FR-015**: The system MUST store VPN keys only in the existing secrets system and must not place them in plaintext configuration.
|
||||
- **FR-007**: The system MUST create service users and groups for deployment workflows and grant SSH access via specified public keys.
|
||||
- **FR-008**: The system MUST configure SSH access for all standard admin hosts and update the VPS connection target to the new public IP.
|
||||
- **FR-016**: The system MUST grant SSH access only to workstation, server, deacero, and galaxy admin hosts.
|
||||
- **FR-017**: The system MUST configure SSHD to use a non-default port and disable root/password authentication to match the existing VPS security posture.
|
||||
- **FR-018**: The system MUST harden remote rebuild access by using a non-root SSH user with least-privilege access for rebuild operations.
|
||||
- **FR-009**: The system MUST update dependent host configurations so existing VPN client connections target the new VPS.
|
||||
- **FR-010**: The system MUST review provided history logs and produce a clarification list of potential missing configurations.
|
||||
- **FR-011**: The system MUST document migration steps for the analytics service and include them in the migration plan.
|
||||
|
||||
Reference in New Issue
Block a user