GPUS IT StatusGreenpeace USA

Operational
v1.0 · 2026-03-10
Servers
7/7
SKY · RAIN · SUN · WIND · OAK · MAPLE · CEDAR
CIS Compliance
100%
193/193 WDC + GCP
Cloud VPN
ESTABLISHED
130.211.194.72 ↔ 38.140.146.68
DNS Serial
2026031002
DNSSEC signed · 134 records
DHCP Hosts
112
Reservations active
Failover
NORMAL
SKY primary · RAIN secondary
All Infrastructure — WDC + GCP
DNS Queries (7 days)
Server Uptime % — All 7
DHCP Leases Active
On-Prem — WDC Servers
SKY — 192.168.120.1
Primary DNS/DHCP · sky.wdc.us.gl3
Online
CIS
47/47
SELinux
Enforcing
Auditd
Immutable
named ✓dhcpd ✓fail2ban ✓auditd ✓rsyslog ✓firewalld ✓chronyd ✓AIDE ✓DNSSEC ✓
RN
RAIN — 192.168.120.2
Secondary DNS/DHCP · rain.wdc.us.gl3
Online
CIS
47/47
SELinux
Enforcing
Zone Sync
Current
named ✓dhcpd ✓fail2ban ✓auditd ✓rsyslog ✓firewalld ✓chronyd ✓AIDE ✓
SN
SUN — 192.168.120.3
Monitoring · Prometheus + Grafana
Online
CIS
48/48
Targets
5
Alerts
0
prometheus ✓grafana ✓node_exporter ✓auditd ✓firewalld ✓chronyd ✓AIDE ✓
WD
WIND — 192.168.120.4
Logging · ELK Stack
Online
CIS
51/51
Indices
5
Retention
90d
elasticsearch ✓logstash ✓kibana ✓auditd ✓firewalld ✓chronyd ✓AIDE ✓
Cloud — GCP (us-central1)
VPN Tunnel ESTABLISHED
WDC 38.140.146.68 ↔ GCP 130.211.194.72 · IKEv2 · AES-256
192.168.120.0/23 + 192.168.124.0/24 ↔ 172.16.0.0/24
GCP VMs — cloud.us (us-central1-a)
OA
OAK — 172.16.0.10
Security Scanner · OpenVAS/Greenbone · oak.cloud.us
Online
docker ✓fail2ban ✓auditd ✓SELinux ✓firewalld ✓chronyd ✓AIDE ✓
MA
MAPLE — 172.16.0.12
Cloud Monitoring · Prometheus + Grafana + Wazuh · maple.cloud.us
Online
prometheus ✓grafana ✓wazuh-mgr ✓fail2ban ✓auditd ✓SELinux ✓firewalld ✓chronyd ✓AIDE ✓
CE
CEDAR — 172.16.0.13
Cloud Logging · ELK Stack + Wazuh Indexer · cedar.cloud.us
Online
elasticsearch ✓logstash ✓kibana ✓fail2ban ✓auditd ✓SELinux ✓firewalld ✓chronyd ✓AIDE ✓
Cloud Run Services
ServiceCloud Run NameImageURLStatus
MkDocs Portalgpus-mkdocs-portalmkdocs:latestinfra.greenpeace.us✅ Running
Status Sitegpus-status-sitestatus-site:lateststatus.greenpeace.us✅ Running
Status Backendgpus-status-backendstatus-backend:latest(internal)✅ Running
Security Sitegpus-security-sitesecurity-site:latestsecurity.greenpeace.us✅ Running
Security Backendgpus-security-backendsecurity-backend:latest(internal)✅ Running
SOC Sitegpus-soc-sitesoc-site:latestsoc.greenpeace.us✅ Running
SOC Backendgpus-soc-backendsoc-backend:latest(internal)✅ Running
Forms Portal Backendgpus-forms-backendgpus-forms-backend:latestforms.greenpeace.us✅ Running
All 8 services scale to zero when idle. TLS is Google-managed. Images in Artifact Registry at us-central1-docker.pkg.dev/gpus-infra/gpus-images.
98
Security Posture Score
CIS compliance · monitoring coverage · backup health · threat activity
CIS Compliance
100%
193/193 WDC + GCP
Uptime (30d)
99.9%
All services
Open Incidents
0
Last: none
Assets Monitored
136
of 138 (98.6%)
Backups
OK
Daily + GCS offsite
Threats
0
Active
CIS Compliance — Per Server
SKY
47/47
100% ✓
RAIN
47/47
100% ✓
SUN
48/48
100% ✓
WIND
51/51
100% ✓
GCP VMs — CIS Compliance
OAK
47/47
100% ✓
MAPLE
47/47
100% ✓
CEDAR
47/47
100% ✓
GCP Cloud Controls
🔐
Data Encryption
VPN AES-256 · GCS encryption at rest · Cloud Run HTTPS
CIS 3.11 PCI 4.1
🔥
VPC Firewall
Default deny-all · VPN + internal rules only
CIS 4.4 PCI 1.2.2
📊
Audit Logging
VPC Flow Logs · Cloud Audit Logs automatic
CIS 8.3 NIST AU-6
🔄
Data Recovery
GCS Nearline · 90-day retention · versioning
CIS 11.1 NIST CP-9
🔀
Network Segmentation
VPC 172.16.0.0/24 · VPN-only from on-prem
CIS 12.4 NIST SC-7
🛡
Transmission Security
IKEv2 · AES-256 · SHA-256 · DH14
NIST SC-8 PCI 1.5.1
Risk Register
Disaster Recovery Plan not documented
IT
Incident Response Plan not documented
IT
SSO not implemented — 42 apps need Okta
IT
Backup pipeline to GCS not configured
IT
Data classification not started — 7 payment + 42 supporter-data apps
IT/Legal
Servers Backed Up
of 7 total
GCS Bucket
gpus-infra-backups-wdc
us-central1 · Nearline
Retention
90d
Daily backups
Last Checked
Live from backend
Backup Status — All Servers
ServerLast BackupSizeAgeGCSNAS
Loading backup data...
Backup Schedule
ServerFrequencyTargetRetention
SKY / RAINDaily 02:00NAS (vmstorage) + GCS90 days
SUN / WINDDaily 02:00NAS (vmstorage) + GCS90 days
OAK / MAPLE / CEDARDaily 02:00GCS (instance SA)90 days
Portal sitesDaily 02:30GCS (mkdocs/status/security)30 days
Portal Site Backups — GCS
SiteURLLast BackupSizeAgeGCS
Loading portal backup data...
CIS Controls v8
100%
193/193 WDC + GCP
PCI-DSS v4.0
94%
47/50 requirements met
NIST CSF
96%
Identify · Protect · Detect · Respond · Recover
NIST SP 800-53
92%
Key controls mapped
Last Audit
2026-03-10
All servers verified
Gaps
3
DRP · IRP · Backup pipeline
CIS Controls v8 — Implementation Status
On-Premises Infrastructure — SKY / RAIN / SUN / WIND
CIS #ControlSKYRAINSUNWINDImplementation
1.1Asset InventoryDHCP lease tracking, DNS records, Kibana dhcp-leases-* index
1.2Software InventoryMinimal RPM install, dnf history tracked
2.2Authorized SoftwareServer base only, no GUI, no unnecessary packages
3.11Data EncryptionDNSSEC, Webmin TLS, SSH key auth, VPN AES-256
3.14Sensitive DataDNSSEC keys chmod 600, ES on dedicated partition
4.1Secure ConfigurationCIS Benchmark Rocky Linux 8 Level 2 applied
4.4Firewallfirewalld default drop zone, explicit rich-rules only
5.1Account Inventorydnsadmin / monitadmin only, service accounts nologin
5.2Privileged Accesssudo with logging, SSH no root, key-only
5.4Password Policy14-char min, 90-day max, lockout after 5
6.1Access ControlSELinux enforcing, BIND chroot, MAC filtering
7.1Vulnerability Mgmtdnf-automatic security updates enabled
8.2Audit Log Mgmtauditd immutable (-e 2), DNS/DHCP/auth rules
8.3Log StorageDedicated /var/log + /var/log/audit on sdb
8.5Log AnalysisKibana dashboards, Grafana panels
8.9Centralized Loggingrsyslog → CEDAR:5140 (GCP) + WIND:5140 (WDC) → Logstash → ES → Kibana
10.1Malware DefensesAIDE daily file integrity monitoring
11.1Data RecoveryDaily cron backups to /backup + GCS (planned)
12.1Network SecurityProd/mgmt separation, firewalld drop, IPv6 disabled
12.4Network Segmentation120.0/23 prod, 124.0/24 mgmt, 172.16.0.0/24 GCP
13.1Threat DetectionFail2ban, AIDE alerts, Prometheus alerting
GCP Cloud Infrastructure — gpus-infra
CIS #ControlStatusImplementation
3.11Data EncryptionVPN AES-256, GCS encryption at rest, Cloud Run HTTPS
4.4FirewallVPC deny-all default, explicit VPN + internal rules
8.3Log StorageVPC Flow Logs, Cloud Audit Logs automatic
11.1Data RecoveryGCS backups Nearline, 90-day retention, versioning
12.4Network SegmentationSeparate VPC 172.16.0.0/24, VPN-only from on-prem
PCI-DSS v4.0 — Compliance Matrix
Payment Card Industry Data Security Standard
ReqSubDescriptionStatusImplementation
11.1.1Network security controls definedfirewalld default-drop zone all servers
11.2.1Inbound/outbound restrictedRich rules per service/source
11.2.2All other traffic deniedZone=drop, no implicit permits
11.3.1Inbound to CDE restrictedDNS/DHCP/SSH from internal only
11.4.1NSC between zonesDHCP failover 647 SKY↔RAIN only
11.5.1Remote access securedSSH key auth, no root, AllowUsers, VPN
22.2.1Securely configuredCIS Benchmark Level 2 applied
22.2.2Vendor defaults changedRoot locked, all defaults changed
22.2.3Unnecessary services removedtelnet/ftp/rsh/avahi/cups masked
22.2.4Insecure protocols disabledSSHv2 only, no FTP/Telnet/rsh
44.1Strong cryptography for transmissionDNSSEC, TLS Webmin, VPN AES-256
55.2Anti-malware mechanismsAIDE file integrity daily scan
77.1Access limited to needDedicated admin accounts, nologin service accounts
88.3.6Password complexity14-char min, 90-day max, lockout after 5
1010.2Audit trailsauditd immutable mode, DNS/DHCP/auth rules
1010.3Audit trail protectionCentralized to WIND (WDC) + CEDAR (GCP), 90-day retention
1010.7Log retentionDedicated log partitions on sdb
1111.5.1File integrity monitoringAIDE daily scans on all 7 servers
1212.1.1Security policy establishedPolicy drafted in status site — formal sign-off pending
1212.5.1Asset inventoryIAR: 136 assets tracked in wdchostregistry.csv (129 workstations + 7 servers)
1212.10.1IR planIRP drafted in status site — formal sign-off pending
NIST Cybersecurity Framework — Function Coverage
Identify
100%
Asset mgmt · Risk assessment · Governance
Protect
100%
Access ctrl · Encryption · Hardening
Detect
100%
AIDE · auditd · ELK · Prometheus
Respond
85%
IRP drafted · formal sign-off pending
Recover
85%
DRP drafted · GCS pipeline pending
NIST SP 800-53 — Key Control Families
FamilyControlStatusImplementation
AC-3Access EnforcementSELinux enforcing, BIND chroot, MAC DHCP filtering
AU-2Auditable Eventsauditd custom rules: DNS/DHCP changes, auth, privilege escalation
AU-6Audit ReviewKibana dashboards (WIND + CEDAR), Grafana panels (SUN + MAPLE), centralized logging
CM-2Baseline ConfigurationCIS Benchmark L2, Terraform IaC for GCP
CM-7Least FunctionalityMinimal install, unnecessary services masked, IPv6 disabled
CP-9System BackupDaily cron backups, GCS offsite (pipeline pending)
IA-2Identification & AuthSSH key-only, no passwords, AllowUsers directive
IA-5Authenticator Mgmt14-char min, 90-day rotation, faillock after 5
SC-7Boundary ProtectionProd/mgmt/GCP zone separation, VPN encrypted tunnel
SC-8Transmission ConfidentialityIKEv2 AES-256, DNSSEC, TLS on Webmin
SC-20Secure Name ResolutionDNSSEC zone signing + validation
SC-28Protection of Info at RestDedicated partitions, GCS encryption, key chmod 600
SI-4System MonitoringPrometheus q15s, Fail2ban, AIDE, Kibana dashboards
SI-7Software IntegrityAIDE daily file integrity scan on all 7 servers
Compliance Gaps & Remediation
PCI 12.1.1 — Security Policy: Policy drafted in Governance tab. Requires formal review and sign-off by management.
Target: Q2 2026
PCI 12.10.1 — IR Plan: IRP drafted in Governance tab. Requires formal review, tabletop exercise, and sign-off.
Target: Q2 2026
NIST CP-9 — Offsite Backup: GCS backup pipeline active — all 4 WDC servers backing up daily to NAS + GCS. GCP VMs backup cron pending.
WDC: ✓ Done
SSO Integration: 42 applications identified for Okta SSO. Not yet started.
Target: Q3 2026
Data Classification: 7 payment + 42 supporter-data apps identified. Classification program not started.
Target: Q3 2026
Estimated Monthly
$362
Apr 2026 · 7 servers + 8 Cloud Run services
VPN (Fixed)
$43
Tunnel + Static IP · largest fixed cost
GCP VMs (3x)
$207
OAK (n2-std-2) + MAPLE (e2-std-2) + CEDAR (e2-std-4)
Budget Alert
$400
GCP Console → Billing → Budgets
Spend Forecast — Apr/May 2026
Cost Breakdown by Service
OAK (n2-standard-2)
$62.00
MAPLE (e2-standard-2)
$48.00
CEDAR (e2-standard-4)
$97.00
SSD Disks (6 × 50GB)
$51.00
Cloud NAT
$15.00
Cloud Run (8 services)
$8.00
Cloud Storage
$5.00
Networking + Egress
$25.00
VPN Tunnel
$36.00
Static IP
$7.00
Artifact Registry
$2.00
Other
$6.00
Cost Details
ResourceSKUUnitQtyRateMonthly
OAK — n2-standard-2oak (us-central1-a)hr730$0.085$62.00
MAPLE — e2-standard-2maple (us-central1-a)hr730$0.067$48.00
CEDAR — e2-standard-4cedar (us-central1-a)hr730$0.134$97.00
SSD Disks (6 × 50GB)pd-ssdGB300$0.170$51.00
Cloud NATgpus-nat-gatewayhr730$0.020$15.00
Cloud VPN Tunnelgpus-vpn-tunnel-wdchr730$0.049$36.00
Static IPgpus-vpn-iphr730$0.010$7.00
Networking + Egressinter-region + internetGB~150varies$25.00
Cloud Run (8 services)mkdocs + status + security + soc + formsreq~2000$0.40/M$8.00
Cloud Storagegpus-infra-backups-wdc + tf-stateGB~300$0.02$5.00
Artifact Registrygpus-imagesGB~10$0.10$2.00
Other (Logging, DNS, VPC)misc$6.00
Total Estimated Monthly$362.00
Cost Optimization Notes
✓ Cloud Run scales to zero — 8 services cost only ~$8/mo total
✓ Nearline storage — 50% cheaper than Standard for backup data
⚠ GCP VMs are the biggest cost — OAK (n2-std-2) + MAPLE (e2-std-2) + CEDAR (e2-std-4) + disks = $258/mo (71% of total)
✓ Single VPN tunnel — upgrade to HA VPN ($72/mo) if uptime SLA needed
✓ SOC dashboard live — soc.greenpeace.us deployed with Wazuh/OpenVAS/Lynis/AIDE/Fail2ban/Prometheus feeds
⚠ Budget alert set to $400/mo — review in GCP Console → Billing → Budgets
Yearly Total
0.018
tCO₂e · Dec 2024 – Mar 2026
Latest Month
0.008
▲ +167% MoM (Mar 2026)
Scope 2 (Market)
0.006
Purchased electricity
Scope 3
0.012
Value-chain indirect
Top Region
us-central1
0.014 tCO₂e (78%)
Monthly Emissions Trend (tCO₂e)
Emissions by Scope
Scope 1
0.001
Direct emissions from owned/controlled sources (e.g., on-site generators). Near zero for cloud-only infrastructure.
Scope 2 (Market)
0.006
Indirect emissions from purchased electricity powering GCP data centers. Reduced by Google's renewable energy purchases.
Scope 3
0.012
All other indirect emissions in the value chain — hardware manufacturing, cooling, network infrastructure, employee commuting to data centers.
Emissions by Region
Contextual Comparisons
Total yearly emissions (0.018 tCO₂e ≈ 18 kg CO₂e) are roughly equivalent to:
🚗
≈ 45
miles driven in an average gasoline car
📱
≈ 2,200
smartphone charges
🌳
< 1 tree
needed to absorb yearly emissions
💰
$0.27
to fully offset via carbon credits
Data source: GCP Carbon Footprint · Market-based emissions · Updated monthly
Security Policy
Incident Response Plan
Disaster Recovery Plan
Information Security Policy
GPUS-POL-001 · v1.0 · Effective: 2026-03-10 · Owner: IT Department · Classification: INTERNAL
1. Access Control
All access to infrastructure systems follows the principle of least privilege. Administrative access is restricted to named accounts over the management network (192.168.124.0/24) using SSH key-based authentication only. Root login is disabled on all servers. Service accounts are set to nologin.
ServerAdmin AccountAuth MethodNetwork
SKY / RAINdnsadminSSH key-only192.168.124.0/24
SUN / WINDmonitadminSSH key-only192.168.124.0/24
OAK / MAPLE / CEDARcloudadminSSH key-onlyVPN (10.8.0.0/28)
GCPrajesh.chhetry@greenpeace.usOAuth + IAMIAM roles
2. Change Management
All configuration changes require: (1) backup of affected files, (2) validation before deployment, (3) AIDE baseline update after change, (4) entry in /var/log/asset-inventory.log, (5) DNSSEC re-signing if zone files changed. GCP changes must go through Terraform — no manual console changes.
3. Availability & Redundancy
DNS and DHCP services run in primary/secondary failover (SKY/RAIN). DHCP failover is automatic. DNS zone transfers via AXFR. Monitoring (SUN) and logging (WIND) are single-instance with daily backups. GCP services use Cloud Run with auto-scaling.
4. Logging & Monitoring
All WDC servers forward logs to WIND (on-prem) and CEDAR (GCP) via rsyslog (TCP:5140). All GCP VMs forward logs to CEDAR. Elasticsearch retains logs for 90 days with daily index rotation. Prometheus on SUN and MAPLE scrapes metrics every 15 seconds across all 7 servers. AIDE runs daily integrity scans on all 7 servers. auditd runs in immutable mode. VPC Flow Logs enabled in GCP.
5. Password Policy
ParameterValueCIS Control
Minimum length14 charactersCIS 5.4
Maximum age90 daysCIS 5.4
Lockout threshold5 failed attemptsCIS 5.4
Lockout duration15 minutesCIS 5.4
Password history5 rememberedCIS 5.4
Incident Response Plan
GPUS-IRP-001 · v1.0 · Effective: 2026-03-10 · Owner: IT Department · Classification: INTERNAL
1. Incident Classification
SeverityDescriptionResponse TimeEscalationExamples
P1 CriticalService outage or active breach15 minIT Manager → CISOBoth DNS down, ransomware, data exfil
P2 HighDegraded service or confirmed intrusion attempt1 hrIT ManagerSingle DNS down, AIDE alert, Fail2ban flood
P3 MediumAnomaly requiring investigation4 hrIT TeamUnusual audit events, DNS query spike
P4 LowMinor issue, no impact24 hrIT TeamConfig drift, routine Fail2ban bans
2. Phase 1 — Detection
Detection sources: AIDE file integrity alerts, Fail2ban ban events, auditd rule triggers, Prometheus alert rules, Kibana dashboards, GCP Cloud Audit Logs.
## Check all detection sources # AIDE sudo aide --check # Fail2ban sudo fail2ban-client status sshd # auditd — recent security events sudo ausearch -ts recent -k dns-zone-change -k dhcp-config # Prometheus alerts curl -s http://192.168.120.3:9090/api/v1/alerts | python3 -m json.tool # Kibana — auth failures # Open http://192.168.124.4:5601 → auth-logs-* index
3. Phase 2 — Containment
## Isolate compromised server (example: SKY) # Option A: Block all traffic except failover sudo firewall-cmd --zone=drop --remove-all-rich-rules sudo firewall-cmd --zone=drop --add-rich-rule='rule family="ipv4" source address="192.168.120.2" accept' # Option B: Shut down (RAIN takes over DNS/DHCP automatically) sudo shutdown -h now # Preserve evidence BEFORE remediation mkdir -p /var/log/incident/$(date +%F) sudo cp /var/named/wdc.us.gl3.db* /var/log/incident/$(date +%F)/ sudo ausearch -ts today > /var/log/incident/$(date +%F)/audit.txt sudo aide --check > /var/log/incident/$(date +%F)/aide.txt 2>&1
4. Phase 3 — Eradication
Identify root cause from logs. Remove malicious artifacts. Restore from known-good backup if files were modified. Re-apply CIS hardening if configuration was altered.
5. Phase 4 — Recovery
## Restore from backup BACKUP_DATE="YYYY-MM-DD" tar xzf /backup/dns-dhcp/dns-backup-${BACKUP_DATE}.tar.gz -C /tmp named-checkzone wdc.us.gl3 /tmp/zones/wdc.us.gl3.db sudo cp /tmp/zones/* /var/named/ sudo cp /tmp/dhcpd.conf /etc/dhcp/dhcpd.conf ## Re-sign DNSSEC cd /var/named sudo dnssec-signzone -A -3 $(head -c 500 /dev/urandom | sha1sum | cut -b 1-16) \ -N INCREMENT -o wdc.us.gl3 -t wdc.us.gl3.db sudo rndc reload sudo systemctl restart dhcpd ## Re-baseline AIDE sudo aide --update && sudo mv /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gz
6. Phase 5 — Post-Incident
Post-incident report due within 72 hours. Root cause analysis, timeline, affected systems, remediation actions, lessons learned, process improvements. All evidence preserved in /var/log/incident/.
Contacts
RoleContactEscalation
IT Infrastructure LeadRajesh ChhetryFirst responder for all incidents
IT ManagerP1/P2 escalation within 15min/1hr
CISOP1 escalation, breach notification
Disaster Recovery Plan
GPUS-DRP-001 · v1.0 · Effective: 2026-03-10 · Owner: IT Department · Classification: INTERNAL
1. Recovery Objectives
SystemRTORPORecovery Method
DNS (SKY/RAIN)5 min0 (real-time failover)Automatic — RAIN takes over
DHCP (SKY/RAIN)30 sec0 (real-time failover)Automatic — failover peer
Monitoring (SUN)1 hr15 sec (scrape interval)ESXi snapshot restore
Logging (WIND)1 hr24 hr (daily backup)ESXi snapshot + backup restore
Cloud VPN15 minN/ATerraform redeploy
Cloud Run5 minN/AAuto-healing by GCP
2. Disaster Scenarios
Scenario 1: Single server failure (SKY or RAIN)
Impact: Minimal — failover is automatic. RAIN serves DNS/DHCP if SKY is down and vice versa. Restore failed server from ESXi snapshot within 1 hour.
Scenario 2: Both DNS/DHCP servers down
## Emergency: Deploy from backup on any Rocky Linux 8 box tar xzf /backup/dns-dhcp/dns-backup-LATEST.tar.gz -C /tmp dnf install -y bind dhcp-server cp /tmp/zones/* /var/named/ cp /tmp/dhcpd.conf /etc/dhcp/ cp /tmp/named.conf /etc/ systemctl start named dhcpd
Scenario 3: ESXi host failure
All 4 WDC VMs lost. GCP VMs (OAK/MAPLE/CEDAR) remain operational. Rebuild WDC from backups on replacement ESXi host. Total rebuild time: ~4 hours following the deployment guides (sky-rain + sun-wind docs).
Scenario 4: WDC site loss (fire, flood)
GCP services remain operational. Backups in GCS bucket. DNS can be redirected at Hover. Rebuild on-prem at DR site using GCS backups + Terraform + deployment guides.
Scenario 5: Cloud VPN tunnel down
## Check tunnel status gcloud compute vpn-tunnels describe gpus-vpn-tunnel-wdc --region=us-central1 ## If ESTABLISHED lost — check Meraki side first # Meraki Dashboard → Security & SD-WAN → VPN Status ## Redeploy VPN via Terraform if needed cd ~/terraform/gpus-infra/terraform terraform apply -target=google_compute_vpn_tunnel.wdc_tunnel
3. Backup Schedule
DataFrequencyLocationRetention
DNS zone filesDaily cron/backup + GCS (planned)90 days
DHCP config + leasesDaily cron/backup + GCS (planned)90 days
ES snapshotsDaily/backup + GCS (planned)90 days
Prometheus TSDBDaily/backup90 days
ESXi VM snapshotsWeeklyLocal datastore4 snapshots
Terraform stateEvery applyGCS (gpus-infra-tf-state)5 versions
4. DR Testing Schedule
Quarterly DR tests: Q1 (DNS failover), Q2 (full server restore from backup), Q3 (site failover simulation), Q4 (full tabletop exercise). Results documented and reviewed by IT Manager.
Change Log
2026-04-07
soc.greenpeace.us deployed — SOC dashboard live with Wazuh/OpenVAS/Lynis/AIDE/Fail2ban/Prometheus feedsGCP
2026-03-10 13:51
chronyd fix: denyalldeny all on SUN + WIND · AIDE re-baselinedCONFIG
2026-03-10 13:38
SUN + WIND rebooted — auditd immutable active · CIS 48/48 + 51/51CIS
2026-03-10 11:15
Cloud VPN ESTABLISHED — 130.211.194.72 ↔ 38.140.146.68GCP
2026-03-10 11:00
GCP infra deployed — VPC, VPN, Cloud Run ×2, GCS ×2, Artifact Registry (19 resources)GCP
2026-03-10 10:55
RAIN DHCP updated — 112 reservations · failover normal · AIDE re-baselinedDHCP
2026-03-10 10:49
SKY DNS/DHCP bulk update — 112 workstations · serial 2026031002 · DNSSEC signedDNSDHCP
2026-03-10 10:30
GCP project gpus-infra created · billing linked · APIs enabledGCP
AIDE Baselines
ServerBaselineReasonStatus
SKY2026-03-10 10:49DNS/DHCP bulk update
RAIN2026-03-10 10:55DHCP update
SUN2026-03-10 13:51chronyd fix + reboot
WIND2026-03-10 13:52chronyd fix + reboot
DNSSEC History
DateSerialSigsKSKZSK
2026-03-102026031002280+008+37075+008+06660
Terraform History
DateActionResourcesProject
2026-03-10Initial deploy19 createdgpus-infra
Document Versions
DocumentVersionUpdated
sky-rain-dns-dhcp-infrastructure.mdv2.22026-03-10
sun-wind-monitoring-logging.mdv1.12026-03-10
wdc-infrastructure-architecture-overview.mdv1.22026-03-10
wdchostregistry.csv (IAR)v2.02026-03-10
gpus-it-architecture.htmlv2.12026-03-10
gcp-cloud-infrastructure.mdv1.52026-03-10