Design for Regulatory Approval as Carefully as You Design Your Automation
summary
Raytheon pursues cloud adoption while constraining services to what regulators will approve, using AWS GovCloud and Azure Government for compliant hosting and relying on automation pipelines, dashboards and bosh to produce audit evidence. Compliance focus centers on NIST SP 800-171 and ITAR plus EAR, CUI and FIPS 140-2 certified crypto. Expect platform limits (no full public console), heavy scrutiny for foreign-person access, platform gaps like PCF 2.0 lacking platform ops roles, and large paperwork — about 200 declarations per system — before authorization.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:45Disclaimer
- 1:45About Raytheon
- 2:29Cybersecurity
- 3:03Uneven landscape
- 6:25Regulations
- 9:08Automation
- 16:29General Approach
- 19:54Additional Resources
related talks
47mHow AWS Can Help Navigate Shifts in the Global Regulatory Landscape
48mWhen DevOps Meets Regulation: Integrating 'Continuous' with 'Government'
30mTackling the new paradigm of regulatory compliance in the cloud era
49mArchitecting Security for Regulated Workloads in Hybrid Cloud
12mDoD FedRAMP Equivalency on AWS
45mRegulated and Sovereign : Impact to the Open Source Developer
39mAI Regulations: A Healthy Tension with Innovation or Stifling Bureaucracy?
47mThe Cost of Innovation: Complexities of Software Regulation