mirror of https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git synced 2026-09-18 05:35:53 +03:00

Files

T

mukul975 ef27f026cb feat: enrich 209 skills with MITRE ATLAS, D3FEND, and NIST AI RMF frontmatter

Added structured security framework mappings to SKILL.md frontmatter across all applicable skills:
- atlas_techniques: MITRE ATLAS v5.5 AML.TXXXX IDs (81 skills, AI-targeted attack techniques)
- d3fend_techniques: MITRE D3FEND v1.3 defensive technique labels (139 skills, mapped from ATT&CK IDs)
- nist_ai_rmf: NIST AI RMF 1.0 subcategory IDs (85 skills, AI risk management functions)

Also updates ATTACK_COVERAGE.md with coverage statistics for all three frameworks.

2026-04-06 01:56:17 +02:00

2.5 KiB

Raw Blame History

name, description, domain, subdomain, tags, version, author, license, nist_ai_rmf, atlas_techniques

name

description

domain

subdomain

Performing GCP Penetration Testing with GCPBucketBrute

Overview

This skill covers Google Cloud Platform security testing using GCPBucketBrute for storage bucket enumeration and access permission testing, combined with gcloud CLI IAM enumeration to identify privilege escalation paths. The approach tests for publicly accessible buckets, overly permissive IAM bindings, and service account key exposure.

When to Use

When conducting security assessments that involve performing gcp penetration testing with gcpbucketbrute
When following incident response procedures for related security events
When performing scheduled security testing or auditing activities
When validating security controls through hands-on testing

Prerequisites

Python 3.8+ with google-cloud-storage library
GCPBucketBrute installed from RhinoSecurityLabs GitHub
gcloud CLI authenticated with test credentials
Authorized penetration testing scope for target GCP project
google-api-python-client and google-auth libraries

Steps

Enumerate Storage Buckets — Use GCPBucketBrute with keyword permutations to discover accessible GCP storage buckets
Test Bucket Permissions — Call TestIamPermissions API on each discovered bucket to determine read/write/admin access levels
Audit IAM Bindings — Enumerate project-level IAM policies to identify overly permissive role bindings
Check Service Account Keys — Identify service accounts with user-managed keys and test for privilege escalation via impersonation
Test Privilege Escalation Paths — Check for iam.serviceAccounts.actAs, setIamPolicy, and other privilege escalation vectors
Generate Findings Report — Produce a structured security assessment with risk severity ratings

Expected Output

JSON report of discovered buckets with permission levels
IAM privilege escalation path analysis
Service account security assessment
Risk-scored findings with remediation recommendations

2.5 KiB Raw Blame History