Back to catalog
Static reviewDevelopment

Skill dossier

performing-physical-intrusion-assessment

Source declaration

Conduct authorized physical penetration testing against facilities, server rooms, and restricted areas using tailgating, RFID badge cloning, lock bypassing, rogue network device deployment, and security-guard procedure testing. Use as part of a full-scope red team engagement to evaluate physical security controls and their path to network access, always under signed client authorization.

The author's original description, preserved in English. It describes intent, not verified performance.

Conduct authorized physical penetration testing against facilities, server rooms, and restricted areas using tailgating, RFID badge cloning, lock bypassing, rogue network device deployment, and security-guard procedure testing. Use as part of a full-scope red team engagement to evaluate physical security controls and their path to network access, always under signed client authorization.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Conduct authorized physical penetration testing against facilities, server rooms, and restricted areas using tailgating, RFID badge cloning, lock bypassing, rogue network device deployment, and security-guard procedure testing. Use as part of a full-scope red team engagement to evaluate physical security controls and their path to network access, always under signed client authorization. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Source-declared purpose: Conduct authorized physical penetration testing against facilities, server rooms, and restricted areas using tailgating, RFID badge cloning, lock bypassing, rogue network device deployment, and security-guard procedure testing. Use as part of a full-scope red team engagement to evaluate physical security controls and their path to network access, always under signed client authorization. [Evidence: skills/performing-physical-intrusion-assessment/SKILL.md:L1-L33]
  • Provisional classification: category and tags are inferred from names, descriptions, and file paths, not verified outcomes. [Evidence: skills/performing-physical-intrusion-assessment/SKILL.md:L1-L33]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/performing-physical-intrusion-assessment/SKILL.md:L1-L33]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
43 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-physical-intrusion-assessment/assets/template.mdReference1.3 KB
skills/performing-physical-intrusion-assessment/LICENSEOther11 KB
skills/performing-physical-intrusion-assessment/references/api-reference.mdReference1.4 KB
skills/performing-physical-intrusion-assessment/references/standards.mdReference1.4 KB
skills/performing-physical-intrusion-assessment/references/workflows.mdReference4.5 KB
skills/performing-physical-intrusion-assessment/scripts/agent.pyScript6.9 KB
skills/performing-physical-intrusion-assessment/scripts/process.pyScript8.5 KB
skills/performing-physical-intrusion-assessment/SKILL.mdInstruction8 KB

SKILL.md frontmatter

{
  "name": "performing-physical-intrusion-assessment",
  "description": "Conduct authorized physical penetration testing against facilities, server rooms, and restricted areas using tailgating, RFID badge cloning, lock bypassing, rogue network device deployment, and security-guard procedure testing. Use as part of a full-scope red team engagement to evaluate physical security controls and their path to network access, always under signed client authorization.",
  "domain": "cybersecurity",
  "subdomain": "red-teaming",
  "tags": [
    "physical-security",
    "red-team",
    "tailgating",
    "badge-cloning",
    "lock-picking",
    "rfid",
    "physical-pentest"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "d3fend_techniques": [
    "Platform Hardening",
    "Hardware Component Inventory",
    "Electromagnetic Radiation Hardening",
    "RF Shielding",
    "Asset Inventory"
  ],
  "nist_csf": [
    "ID.RA-01",
    "GV.OV-02",
    "DE.AE-07"
  ],
  "mitre_attack": [
    "T1595",
    "T1190",
    "T1059",
    "T1078",
    "T1027"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    MITRE ATT&CK Mapping

    Source-described action candidate under “MITRE ATT&CK Mapping”; not verified execution.

  4. 04
    Action

    Physical Security Testing Toolkit

    Source-described action candidate under “Physical Security Testing Toolkit”; not verified execution.

  5. 05
    Action

    Technique 1: Tailgating

    Source-described action candidate under “Technique 1: Tailgating”; not verified execution.

  6. 06
    Action

    Technique 2: Badge Cloning

    Source-described action candidate under “Technique 2: Badge Cloning”; not verified execution.

Inspect all extracted workflow candidates (33 candidate steps)
  1. 07
    Action

    Position near badge reader (elevator, door entry)

    Source-described action candidate under “Technique 2: Badge Cloning”; not verified execution.

  2. 08
    Input

    Read badge wirelessly as employee passes (1-3 second window)

    Source-described input candidate under “Technique 2: Badge Cloning”; not verified execution.

  3. 09
    Action

    Clone to blank card

    Source-described action candidate under “Technique 2: Badge Cloning”; not verified execution.

  4. 10
    Action

    Use cloned badge to access secured areas

    Source-described action candidate under “Technique 2: Badge Cloning”; not verified execution.

  5. 11
    Action

    Document which areas were accessible

    Source-described action candidate under “Technique 2: Badge Cloning”; not verified execution.

  6. 12
    Action

    Technique 3: Lock Bypassing

    Source-described action candidate under “Technique 3: Lock Bypassing”; not verified execution.

  7. 13
    Action

    Technique 4: Rogue Device Deployment

    Source-described action candidate under “Technique 4: Rogue Device Deployment”; not verified execution.

  8. 14
    Action

    Technique 5: Dumpster Diving

    Source-described action candidate under “Technique 5: Dumpster Diving”; not verified execution.

  9. 15
    Action

    Assessment Methodology

    Source-described action candidate under “Assessment Methodology”; not verified execution.

  10. 16
    Action

    Perimeter walk - identify all entry points, cameras, guard posts

    Source-described action candidate under “Pre-Assessment Reconnaissance”; not verified execution.

  11. 17
    Action

    Observe employee patterns - shift changes, break schedules

    Source-described action candidate under “Pre-Assessment Reconnaissance”; not verified execution.

  12. 18
    Action

    Identify badge technology (HID, MIFARE, iCLASS)

    Source-described action candidate under “Pre-Assessment Reconnaissance”; not verified execution.

  13. 19
    Action

    Map camera coverage and blind spots

    Source-described action candidate under “Pre-Assessment Reconnaissance”; not verified execution.

  14. 20
    Action

    Note security guard patrol routes and timing

    Source-described action candidate under “Pre-Assessment Reconnaissance”; not verified execution.

  15. 21
    Action

    External perimeter: Fencing, gates, parking barriers

    Source-described action candidate under “Execution Phases”; not verified execution.

  16. 22
    Action

    Building entry: Main entrance, side doors, loading dock

    Source-described action candidate under “Execution Phases”; not verified execution.

  17. 23
    Action

    Internal access: Floor access, elevator controls

    Source-described action candidate under “Execution Phases”; not verified execution.

  18. 24
    Action

    Restricted areas: Server rooms, executive offices, data centers

    Source-described action candidate under “Execution Phases”; not verified execution.

  19. 25
    Action

    Device deployment: Network implants, rogue wireless

    Source-described action candidate under “Execution Phases”; not verified execution.

  20. 26
    Action

    Ethical and Safety Considerations

    Source-described action candidate under “Ethical and Safety Considerations”; not verified execution.

  21. 27
    Decision

    Always carry authorization letter - Be prepared to identify yourself immediately if confronted

    Source-described decision candidate under “Ethical and Safety Considerations”; not verified execution.

  22. 28
    Decision

    Never force entry - If a technique damages property, document and skip

    Source-described decision candidate under “Ethical and Safety Considerations”; not verified execution.

  23. 29
    Decision

    Immediate stop if law enforcement is called before deconfliction

    Source-described decision candidate under “Ethical and Safety Considerations”; not verified execution.

  24. 30
    Action

    Never photograph individuals without authorization

    Source-described action candidate under “Ethical and Safety Considerations”; not verified execution.

  25. 31
    Action

    Document, don't exploit - Take photos as evidence, don't steal actual data

    Source-described action candidate under “Ethical and Safety Considerations”; not verified execution.

  26. 32
    Action

    Safety first - Do not enter hazardous areas or bypass fire safety

    Source-described action candidate under “Ethical and Safety Considerations”; not verified execution.

  27. 33
    Action

    References

    Source-described action candidate under “References”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

24 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

4 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 4 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

19 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 19 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Downloaded content may be executed

This line combines retrieval and execution. Such patterns can run mutable remote code. Review pinning, integrity checks, and isolation; the analyzer performed no download or execution. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/performing-physical-intrusion-assessment/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/performing-physical-intrusion-assessment/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/performing-physical-intrusion-assessment
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.