feat(tyr): complete vpc-sc and private access setup
This commit is contained in:
parent
221b055f95
commit
43d3533c32
|
|
@ -11,6 +11,10 @@ This document tracks the high-level goals and future development milestones for
|
|||
- [x] Bootstrap SPIRE
|
||||
- [x] Establish Binary Authorization Infrastructure
|
||||
|
||||
## Phase 2: Network Hardening & Perimeter Defense
|
||||
- [x] Establish GCP VPC Service Controls (VPC-SC) perimeter.
|
||||
- [x] Configure Private Service Connect (PSC) for all Google APIs.
|
||||
|
||||
## Phase 3: Memory Bank & Project Management
|
||||
- [x] Implement `read_memory_bank` and `write_memory_bank` MCP tools.
|
||||
- [x] Implement `build_and_deploy_service` MCP tool.
|
||||
|
|
|
|||
|
|
@ -11,3 +11,11 @@
|
|||
- **Phase 1.4: Binary Authorization**
|
||||
- Status: **Complete**
|
||||
- Notes: KMS key, attestor, and policy are created and active.
|
||||
|
||||
- **Task 2.1: Establish VPC-SC Perimeter**
|
||||
- Status: **Complete**
|
||||
- Notes: Created `tyr_perimeter` to restrict Cloud Run and Artifact Registry.
|
||||
|
||||
- **Task 2.2: Enable Private Google Access**
|
||||
- Status: **Complete**
|
||||
- Notes: Enabled Private Google Access on the default subnet in `us-central1`.
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user