Under Section 4.2 of the Master Subscription Agreement, Client provides authorized engineering personnel with dedicated wireless access and outbound HTTPS connectivity to ensure deployment milestones execute on schedule:
| Status | Item / Requirement | Technical Specifications & Verification Guidance |
|---|---|---|
| Dedicated Contractor / Guest Wi-Fi SSID | Provision wireless network credentials for Strata field engineers at the plant administration building, control room annex, and engineering trailers. | |
| Unrestricted Outbound HTTPS (Port 443) | Wi-Fi subnet permits outbound TLS 1.3 on TCP Port 443 to external container registries (gcr.io, pkg.dev, ghcr.io) and engineering endpoints (*.stratacarbonassurance.com). |
|
| TLS Deep-Packet Inspection Exemption | Confirm corporate proxy or firewall does not strip mutual TLS (mTLS) certificates or container image pull signatures on outbound Port 443 from Strata laptops. | |
| DMZ Jump Host / Bastion Reachability | Ensure Strata engineering laptops on designated Wi-Fi (or via Client VPN) can reach Level 3.5 DMZ staging hosts via SSH (Port 22) or RDP (Port 3389). |
Strata executes compute inside Client's cloud boundary with zero raw telemetry egress. Confirm cloud infrastructure readiness:
| Status | Control Domain | Readiness Requirement |
|---|---|---|
| Target VPC & Private Subnet | Dedicated private subnet in Client's cloud account with outbound NAT gateway (Port 443) for container image pulls and emitting signed Merkle roots. | |
| 15-Year WORM Storage Bucket | Client-owned S3 bucket (with S3 Object Lock in COMPLIANCE mode) or GCS bucket (with Bucket Lock) encrypted with Client KMS Customer-Managed Key. | |
| Deployment IAM Role / Service Principal | Scoped deployment role granted to Strata lead engineer to execute Terraform / Helm deployment of enclave runtime containers. |
Deployment strictly enforces Purdue Level 3.5 read-only boundaries with zero control-loop write capability:
| Status | OT Security Control | Configuration & Verification Standard |
|---|---|---|
| Zero Inbound Firewall Rules Confirmed | Verify plant firewall denies all inbound connections from DMZ to control networks. DMZ collector initiates outbound HTTPS GET requests only. | |
| Read-Only Service Account (SVC_STRATA_RO) | Active Directory / Kerberos or PI Security identity created with Read Data strictly scoped to target Asset Framework tree (Write Data explicitly denied). | |
| Asset Framework Template Imported | Strata_Compliance_Facility_Template.xml imported into PI AF with the 12-18 core custody flow, check meter, and wellhead tags mapped. |
|
| 72-Hour DMZ Spool Disk Allocated | DMZ utility VM provisioned with at least 20 GB dedicated SSD storage for SQLite WAL ring-buffer to guarantee telemetry continuity across WAN outages. |
Plant IT/OT and network coordinators confirm the provisions above are scheduled or active prior to on-site engineering kickoff:
| PLANT IT / OT COORDINATOR CONFIRMATION | STRATA DEPLOYMENT LEAD CONFIRMATION |
|---|---|
| Assigned Wi-Fi SSID: ________________________________ | Deployment Lead: Jeffrey Anthony Mendonca |
| DMZ Staging Jump Host IP: ___________________________ | Target Kickoff Date: _____________________________ |
| Coordinator Name: ________________________________ | Signature: _______________________________________ |
| Coordinator Title: _______________________________ | Verification Date: ________________________________ |
| Signature: _______________________________________ | Status: Ready for 30-Day Core Launch |