implementing-zero-trust-with-beyondcorp

implementing-zero-trust-with-beyondcorp is a skill for Claude Code from oyi77/1ai-skills. It costs 73 tokens per session (1,115 once invoked), scanned A, original, MIT.

A deployment guide for Google BeyondCorp Enterprise, which applies zero trust access controls to cloud resources and internal applications. Zero trust means checking every request using identity, device health, and context rather than trusting a network location.

In plain words
What is it for?
It is for configuring Identity-Aware Proxy, defining context-based access policies, validating device trust, and protecting GCP resources and internal web applications.
Why use it?
Being inside a corporate network does not prove that a user or device should access every resource. This approach limits access according to identity and device posture.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the 1ai-skills plugin — 209 skills, 4 commands shipped together

Good fit It is for configuring Identity-Aware Proxy, defining context-based access policies, validating device trust, and protecting GCP resources and internal web applications.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oyi77/1ai-skills/implementing-zero-trust-with-beyondcorp
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add oyi77/1ai-skills --skill implementing-zero-trust-with-beyondcorp
Clone the repo
git clone --depth 1 https://github.com/oyi77/1ai-skills

Made for: Claude Code.

Or install 1ai-skills, the plugin that ships this one along with the rest of its 209 skills, 4 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for implementing-zero-trust-with-beyondcorp

README.md
[![agentmods](https://agentmods.dev/badge/skills/oyi77/1ai-skills/implementing-zero-trust-with-beyondcorp/github.svg)](https://agentmods.dev/skills/oyi77/1ai-skills/implementing-zero-trust-with-beyondcorp)
Your own site
<a href="https://agentmods.dev/skills/oyi77/1ai-skills/implementing-zero-trust-with-beyondcorp"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/implementing-zero-trust-with-beyondcorp/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for implementing-zero-trust-with-beyondcorp

Your own site · 80×15
<a href="https://agentmods.dev/skills/oyi77/1ai-skills/implementing-zero-trust-with-beyondcorp"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/implementing-zero-trust-with-beyondcorp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,115 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00073 $0.01115
Opus 5 $0.00036 $0.00558
Sonnet 5 $0.00015 $0.00223
Haiku 4.5 $0.00007 $0.00112

Measured 6d ago against content hash 179193a671dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

implementing-zero-trust-with-beyondcorp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

cybersecurity/_deprecated/implementing-zero-trust-with-beyondcorp/SKILL.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

Trigger phrases:

  • "implementing zero trust with beyondcorp"

  • "Deploy Google BeyondCorp Enterprise zero trust access controls using Identity-Aw"

  • 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

When NOT to Use

  • When you lack proper authorization for testing
  • For production systems without change management
  • When the task requires legal or compliance expertise beyond technical scope

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

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}

Read the full file on GitHub · 127 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 127 lines · 73 tokens per session scan A 179193a671dc

Subscribe to this mod's changes

implementing-zero-trust-with-beyondcorp is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 1,115 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Related

Other skills, from other repositories

implementing-zero-trust-in-cloud

This skill guides organizations through implementing zero trust architecture in cloud environments following NIST SP 800-207 and Google BeyondCorp principles. It covers identity-centric access controls, micro-segmentation, continuous verification, device trust assessment, and deploying Identity-Aware Proxy to…

xalgorix/xalgorix · 74 tokens

implementing-zero-trust-network-access

Implementing Zero Trust Network Access (ZTNA) in cloud environments by configuring identity-aware proxies, micro-segmentation, continuous verification with conditional access policies, and replacing traditional VPN-based access with BeyondCorp-style architectures across AWS, Azure, and GCP.

xalgorix/xalgorix · 59 tokens

terraform-state-leak

Exploit exposed Terraform state files — secrets, cloud creds, RDS passwords, IAM keys, and infrastructure topology in plain JSON.

PurpleAILAB/Decepticon · 31 tokens

s3-takeover

Detect and claim dangling S3 buckets referenced by subdomains (CNAME → s3 hostnames where bucket no longer exists).

PurpleAILAB/Decepticon · 31 tokens

aws-iam-enum

Enumerate AWS IAM policies, detect privilege escalation paths per Rhino Security Labs canonical 21 primitives.

PurpleAILAB/Decepticon · 25 tokens

implementing-secrets-management-with-vault

This skill covers deploying HashiCorp Vault for centralized secrets management across cloud environments, including dynamic secret generation for databases and cloud providers, transit encryption, PKI certificate management, and Kubernetes integration. It addresses eliminating hardcoded credentials from application…

xalgorix/xalgorix · 69 tokens