mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-08-03 17:30:19 +03:00
Mahipal
2fb6a9faff
Each rewritten description now states both what the skill does (concrete capability, named tools/artifacts) and an explicit when-to-use trigger, improving agent discovery/activation. Grounded in each skill's own body; changes confined to the `description` field only (bodies and all other frontmatter untouched). Produced by a gated audit->rewrite->recheck loop (548 -> 0 flagged) with a sampled anti-invention check (0 ungrounded). Schema: 817/817 pass. Framework-ID gate: 0 defects.
69 lines
2.9 KiB
Markdown
69 lines
2.9 KiB
Markdown
---
|
|
name: implementing-zero-trust-with-beyondcorp
|
|
description: Configures Google BeyondCorp Enterprise Identity-Aware Proxy (IAP) as the access enforcement point for web applications, defining Access Context Manager access levels from device trust and network attributes, and auditing the resulting policies for compliance. Use when eliminating perimeter/VPN trust for GCP resources or internal apps, or when setting up identity- and device-posture-based access controls on Google Cloud.
|
|
domain: cybersecurity
|
|
subdomain: zero-trust
|
|
tags:
|
|
- zero-trust
|
|
- beyondcorp
|
|
- google-cloud
|
|
- iap
|
|
- context-aware-access
|
|
- device-trust
|
|
- identity
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_csf:
|
|
- PR.AA-01
|
|
- PR.AA-05
|
|
- PR.IR-01
|
|
mitre_attack:
|
|
- T1078
|
|
- T1550
|
|
- T1021
|
|
- T1556
|
|
- T1078.004
|
|
---
|
|
|
|
# Implementing Zero Trust with BeyondCorp
|
|
|
|
## Overview
|
|
|
|
Google BeyondCorp Enterprise implements the zero trust security model by eliminating the concept of a trusted network perimeter. Instead of relying on VPNs and network location, BeyondCorp authenticates and authorizes every request based on user identity, device posture, and contextual attributes. Identity-Aware Proxy (IAP) serves as the enforcement point, intercepting all requests to protected resources and evaluating them against Access Context Manager policies. This skill covers configuring IAP for web applications, defining access levels based on device trust and network attributes, and auditing access policies for compliance.
|
|
|
|
|
|
## When to Use
|
|
|
|
- When deploying or configuring implementing zero trust with beyondcorp capabilities in your environment
|
|
- When establishing security controls aligned to compliance requirements
|
|
- When building or improving security architecture for this domain
|
|
- When conducting security assessments that require this implementation
|
|
|
|
## Prerequisites
|
|
|
|
- Google Cloud project with BeyondCorp Enterprise license
|
|
- IAP API enabled (iap.googleapis.com)
|
|
- Access Context Manager API enabled (accesscontextmanager.googleapis.com)
|
|
- GCP resources to protect (Compute Engine, App Engine, or GKE services)
|
|
- Endpoint Verification deployed on managed devices
|
|
- Python 3.9+ with google-cloud-iap library
|
|
|
|
## Steps
|
|
|
|
### Step 1: Enable IAP on Target Resources
|
|
Configure Identity-Aware Proxy on Compute Engine, App Engine, or HTTPS load balancer backends.
|
|
|
|
### Step 2: Define Access Levels
|
|
Create Access Context Manager access levels based on IP ranges, device attributes (OS version, encryption, screen lock), and geographic location.
|
|
|
|
### Step 3: Bind Access Policies
|
|
Apply access levels as IAP conditions to enforce context-aware access decisions on protected resources.
|
|
|
|
### Step 4: Audit and Monitor
|
|
Query IAP audit logs, verify policy enforcement, and identify gaps in zero trust coverage.
|
|
|
|
## Expected Output
|
|
|
|
JSON report containing IAP-protected resources, access level definitions, policy binding audit results, and zero trust coverage metrics.
|