SkillAgentSearch skills...

analyzing-cloud-storage-access-patterns

Detect abnormal access in AWS S3, GCS, and Azure Blob Storage by analyzing CloudTrail Data Events, GCS audit logs, and Azure Storage Analytics for after-hours bulk downloads, new-IP access, and API-call spikes (e.g. GetObject) via statistical baselines and time-series anomaly detection

Install / Use

npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-cloud-storage-access-patterns

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Category

Security

Supported Platforms

Universal

Our assessment of analyzing-cloud-storage-access-patterns

analyzing-cloud-storage-access-patterns scores 85/100 on our quality scale, 790th of 1,108 Security skills we index.

Its SKILL.md is 2.3 KB long, split into 6 sections with 2 code examples: moderately detailed.

With 36,115 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
20/30
Structure
16/20
Description
15/15
Adoption
19/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so analyzing-cloud-storage-access-patterns is actively maintained.
  • Our last check on 2026-11-04 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-25. Automated pattern scan on 2026-09-25. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

analyzing-cloud-storage-access-patterns compared with similar skills

All 4 of these similar skills score higher than analyzing-cloud-storage-access-patterns; compare them before choosing.

SkillScoreStarsUpdatedFormat
analyzing-cloud-storage-access-patterns (this skill)by mukul9758536.1k3mo agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server
crawl4aiby unclecode10087.4k3d agoMCP Server

Frequently asked questions

How do I install analyzing-cloud-storage-access-patterns?
Run npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-cloud-storage-access-patterns. The install tabs above show the steps for each supported agent.
Which AI agents does analyzing-cloud-storage-access-patterns work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is analyzing-cloud-storage-access-patterns safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is analyzing-cloud-storage-access-patterns still maintained?
The repository was last updated about 3 months ago, so analyzing-cloud-storage-access-patterns is actively maintained.

name: analyzing-cloud-storage-access-patterns description: Detect abnormal access in AWS S3, GCS, and Azure Blob Storage by analyzing CloudTrail Data Events, GCS audit logs, and Azure Storage Analytics for after-hours bulk downloads, new-IP access, and API-call spikes (e.g. GetObject) via statistical baselines and time-series anomaly detection. Use when investigating suspected cloud data exfiltration or building related detection rules. domain: cybersecurity subdomain: cloud-security tags:

  • cloud-security
  • aws-s3
  • gcs
  • azure-blob-storage
  • cloudtrail
  • data-access-anomaly
  • exfiltration-detection version: '1.0' author: mahipal license: Apache-2.0 atlas_techniques:
  • AML.T0024
  • AML.T0056 nist_ai_rmf:
  • MEASURE-2.7
  • MAP-5.1
  • MANAGE-2.4 nist_csf:
  • PR.IR-01
  • ID.AM-08
  • GV.SC-06
  • DE.CM-01 mitre_attack:
  • T1530
  • T1567.002
  • T1619
  • T1078.004
  • T1048

Analyzing Cloud Storage Access Patterns

When to Use

  • When investigating security incidents that require analyzing cloud storage access patterns
  • When building detection rules or threat hunting queries for this domain
  • When SOC analysts need structured procedures for this analysis type
  • When validating security monitoring coverage for related attack techniques

Prerequisites

  • Familiarity with cloud security concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

Instructions

  1. Install dependencies: pip install boto3 requests
  2. Query CloudTrail for S3 Data Events using AWS CLI or boto3.
  3. Build access baselines: hourly request volume, per-user object counts, source IP history.
  4. Detect anomalies:
    • After-hours access (outside 8am-6pm local time)
    • Bulk downloads: >100 GetObject calls from single principal in 1 hour
    • New source IPs not seen in the prior 30 days
    • ListBucket enumeration spikes (reconnaissance indicator)
  5. Generate prioritized findings report.
python scripts/agent.py --bucket my-sensitive-data --hours-back 24 --output s3_access_report.json

Examples

CloudTrail S3 Data Event

{"eventName": "GetObject", "requestParameters": {"bucketName": "sensitive-data", "key": "financials/q4.xlsx"},
 "sourceIPAddress": "203.0.113.50", "userIdentity": {"arn": "arn:aws:iam::123456789012:user/analyst"}}

Related Skills

View on GitHub
GitHub Stars36.1k
CategorySecurity
Updated2mo ago
Forks4.4k

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions