Skip to content

fix(blueprints): harden IAM, CMEK, firewall, and service accounts in IL5 and FedRAMP High - #346

Closed
aghassemlouei wants to merge 1 commit into
mainfrom
fix/blueprints-il5-and-fedramp-high-hardening
Closed

aghassemlouei wants to merge 1 commit into
mainfrom
fix/blueprints-il5-and-fedramp-high-hardening

Conversation

@aghassemlouei

Copy link
Copy Markdown
Member

Description

Hardens IAM bindings, customer-managed encryption keys (CMEK), firewall rules, and dedicated service accounts across blueprints/fedramp-high/ and blueprints/il5/:

  • Scope Document AI, Cloud Translation, Cloud Run, Cloud Functions, Cloud Workstations, Dataflow, and Pub/Sub service account bindings to least-privilege resource-level IAM members.
  • Wire CMEK encryption keys across Cloud Composer, Cloud Spanner, Cloud Translation, Firestore, and Vertex MLOps blueprints.
  • Restrict bastion, PostgreSQL, and GKE firewall rules to explicit target service accounts or tags, enforce HTTPS on GitLab load balancing, and enable private nodes and default node pool removal in il5/gke and il5/gke-hardened.
  • Synchronize README.md variable and output tables via tools/tfdoc.py and add unit test coverage in tests/tools/test_il5_and_fedramp_high_blueprints.py.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Deployment & Compliance Impact

  • Applicable Regimes:
    • US Region Restricted (e.g., Access Policy constraint)
    • FedRAMP Moderate
    • FedRAMP High
    • DoD IL4
    • DoD IL5
    • General / All
  • NIST 800-53r5 Controls: AC-3, AC-6, IA-5, SC-7, SC-8, SC-12, SC-28

Checklist

Code Quality & Reusability

  • My code adheres to the Maximize Reusability principle. I have not redefined common elements and have reused existing base configurations and modules where possible.
  • I have checked that no existing module or configuration in modules/ or fast/stages-aw/ can be leveraged for this change.
  • My code follows the established naming conventions outlined in docs/naming-convention.md.

Documentation

  • I have updated the README.md of the modified module or blueprint.
  • I have added/updated documentation for inputs (variables) and outputs.

Security

  • My change adheres to GCP security best practices and the principle of least privilege.
  • I have ensured compliance with the targeted regime (FedRAMP Moderate, FedRAMP High, IL4, IL5, etc.).

Testing

  • I have tested my changes locally.
  • I have included details of my testing in this PR.

Testing Performed

  • Verified bash tools/lint.sh passes all 10 repository checks (Boilerplate check, Terraform format, Terraform lint, READMEs, Links, FAST Names, Python formatting, Python lint, Blueprint metadata, Version checks).
  • Verified bash tools/run_tests.sh, ruff check ., and ruff format --check . pass with zero errors.

@aghassemlouei aghassemlouei added Bug Something isn't working Framework - FedRAMP High FedRAMP High compliance regime and controls Framework - IL5 DoD Impact Level 5 (IL5) compliance regime and controls Level of Effort - Medium Moderate task requiring thought and testing; typically takes a couple of days to a week Priority - High Critical issues blocking development or users; urgent bugs or core features for release Scope - Blueprint Related to solution blueprints in the blueprints directory Security Something is insecure or can be secured labels Oct 23, 2026
@aghassemlouei
aghassemlouei force-pushed the fix/blueprints-il5-and-fedramp-high-hardening branch from c6778ed to 43e975c Compare October 27, 2026 01:10
@aghassemlouei
aghassemlouei force-pushed the fix/blueprints-il5-and-fedramp-high-hardening branch from 43e975c to bac4051 Compare October 28, 2026 04:09
@aghassemlouei

Copy link
Copy Markdown
Member Author

Rebased onto main (db8271cf), resolving the conflict in blueprints/fedramp-high/gitlab/main.tf by preserving the GKE control plane and node pool settings from #345 alongside the dedicated google_service_account.gke_node_sa and HTTPS load balancer configuration.

@aghassemlouei

Copy link
Copy Markdown
Member Author

Closing this multi-blueprint bundle PR so blueprint fixes can land per blueprint family against current main. The remaining deployment and runtime bugs are tracked in #373 and the IAM, CMEK, and firewall hardening items are tracked in #374 under #33.

@aghassemlouei
aghassemlouei deleted the fix/blueprints-il5-and-fedramp-high-hardening branch October 28, 2026 04:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working Framework - FedRAMP High FedRAMP High compliance regime and controls Framework - IL5 DoD Impact Level 5 (IL5) compliance regime and controls Level of Effort - Medium Moderate task requiring thought and testing; typically takes a couple of days to a week Priority - High Critical issues blocking development or users; urgent bugs or core features for release Scope - Blueprint Related to solution blueprints in the blueprints directory Security Something is insecure or can be secured

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant