tag: Access-Control · 10 items
- Platform/SRE — Plan: If you have automation or multiple admins modifying IAM Identity Center users/groups (via SCIM, AD sync, or API), adopt the new Revision parameter on update/delete calls to prevent silent overwrites; no deadline, but worth scheduling for any identity-management automation this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: A new GA GitHub Enterprise Cloud governance control that tightens human access to sensitive org actions; no infrastructure change required, but worth understanding when designing access-control policies.
- CI/CD — Plan: Evaluate which release and deployment actions qualify as high-impact in your org and whether enabling proof-of-presence would require changes to release-approval workflows; no deadline, but this is a concrete supply-chain hardening step to schedule this quarter.
- Leader — Plan: Evaluate rolling out proof-of-presence as an org-wide GitHub Enterprise Cloud policy to reduce insider-threat and account-takeover risk on sensitive actions; no deadline, but a meaningful security governance improvement to bring into your next planning cycle.
- Platform/SRE — Learn: Conceptual guidance on extending Boundary’s identity-based access controls to AI agent workloads — worth tracking if the platform already runs Boundary, but no new release, deadline, or operational change is cited.
- CI/CD — Skip
- Leader — Learn: Vendor blog framing AI agent governance via Boundary; no licensing change, pricing event, or strategic decision required — relevant context if evaluating secrets/access tooling for an AI platform initiative.
- Platform/SRE — Skip
- CI/CD — Plan: Workflow execution protections are now GA for GitHub Enterprise, orgs, and repos; schedule adoption of allowlist controls to restrict who can trigger workflows as a supply-chain hardening step this quarter.
- Leader — Plan: This GA feature enables org-wide policy on who may trigger GitHub Actions workflows; evaluate adding it to your golden-path security standards and internal developer platform requirements.
- Signals: GA announcement
- Platform/SRE — Learn: Covers OIDC/IdP integration patterns for on-prem Kubernetes clusters where IAM isn’t bundled — useful for evaluating or hardening auth config, but no deadline or breaking change.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: Interesting pattern for zero-trust mainframe access using Boundary workers, but no deadline or GA capability change — worth evaluating if mainframes are in scope for the platform.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: New GA controls for AI agent traffic (stateful authz and rate limiting) are worth evaluating if your platform exposes Bedrock-based agents, but there is no operational urgency or EOL signal.
- CI/CD — Skip
- Leader — Learn: Temporal policies and rate limiting in AgentCore address governance and fairness concerns for AI agent deployments — relevant context for teams standardizing on AWS AI infrastructure, but no strategic decision required now.
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Learn: If your org has standardized on GitHub Copilot, this new dedicated policy gives enterprise and org admins finer-grained control over who can access the Copilot app — worth knowing when setting AI tooling governance standards.
- Platform/SRE — Plan: New GA Neptune capability that replaces static ARN enumeration in IAM policies with attribute-based cluster access using resource and principal tags; plan to adopt TBAC if you operate multiple Neptune clusters in shared VPC environments to enforce team and environment isolation.
- CI/CD — Skip
- Leader — Learn: Neptune now supports attribute-based access governance across clusters via IAM tags, useful context for organizations running Neptune at scale, but no strategic, licensing, or cost decision is triggered.
- Platform/SRE — Learn: Useful reference for SREs managing Grafana Cloud RBAC as observability centralizes across teams, but no operational change required — no EOL, deprecation, or security anchor present.
- CI/CD — Skip
- Leader — Learn: Outlines a scalable access governance model for centralized observability platforms, relevant when evaluating Grafana Cloud as a standard or managing sprawl across cloud/on-prem data sources.