Skip to content
cccskills
FreePublished on GitHub

deploying-software-defined-perimeter

Deploy a Software-Defined Perimeter that connects verified users to authorized applications. Configure single-packet authorization, mutual certificate authentication, access policies, and monitoring, then test whether unauthorized connections and access between applications are blocked.

OriginalShow the original description

Deploys a Software-Defined Perimeter per the CSA v2.0 specification, configuring Single Packet Authorization, mutual TLS, and SDP controller/gateway components to enforce zero trust network access. Use when building or hardening zero trust network architecture, implementing SPA-based "invisible" infrastructure that cloaks services from unauthenticated scanning, or meeting compliance requirements for zero trust network access.

See how to install

Good for

  • Building zero trust access to internal applications
  • Hiding services from unauthenticated network scans
  • Testing certificate authentication and access restrictions
  • Planning SDP monitoring and certificate maintenance

Files included (8)

  • SKILL.md7.9 KB
  • assets/template.md1.5 KB
  • LICENSE11.0 KB
  • references/api-reference.md1.8 KB
  • references/standards.md2.8 KB
  • references/workflows.md5.1 KB
  • scripts/agent.py6.6 KB
  • scripts/process.py10.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Deploying Software-Defined Perimeter

Prerequisites

  • Understanding of zero trust principles (NIST SP 800-207)
  • Knowledge of CSA Software-Defined Perimeter specification
  • Familiarity with PKI and mutual TLS authentication
  • Experience with network security architecture

Overview

A Software-Defined Perimeter (SDP) implements zero trust by creating a dynamically provisioned, identity-centric perimeter around individual resources. Defined by the Cloud Security Alliance (CSA), SDP makes application infrastructure invisible to unauthorized users through a "dark cloud" approach where services are hidden until authenticated and authorized. Unlike traditional VPN, SDP establishes one-to-one encrypted connections between verified users and specific applications.

This skill covers deploying SDP using the CSA v2.0 specification, implementing Single Packet Authorization (SPA), configuring the SDP controller and gateway, and validating the deployment against NIST SP 800-207 requirements.

When to Use

  • When deploying or configuring deploying software defined perimeter 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

  • Familiarity with zero trust architecture 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

Architecture

SDP Components (CSA Specification)

┌─────────────────────┐
│ SDP Controller       │
│ - Authentication     │
│ - Authorization      │
│ - Policy management  │
│ - Key management     │
└──────────┬──────────┘
           │
    ┌──────┴──────┐
    │             │
    v             v
┌────────┐  ┌────────────┐
│ IH     │  │ AH         │
│(Client)│  │(Gateway)   │
│        │  │            │
│ SPA    │──│ Protected  │
│ mTLS   │  │ Resources  │
└────────┘  └────────────┘

IH = Initiating Host (User Device)
AH = Accepting Host (Application Gateway)
SPA = Single Packet Authorization

SDP Deployment Models

  1. Client-to-Gateway: User device connects through SDP gateway to backend applications
  2. Client-to-Server: Direct connection between user and application server
  3. Server-to-Server: Workload-to-workload communication through SDP
  4. Gateway-to-Gateway: Site-to-site connectivity replacing traditional VPN tunnels

Key Concepts

Single Packet Authorization (SPA)

SPA is a network security mechanism where the SDP gateway drops all TCP/UDP packets by default. A cryptographically signed single packet must be sent before any connection is established. The gateway validates the SPA packet, and only then opens a temporary port for the authenticated session. This makes the gateway invisible to port scanners.

Mutual TLS (mTLS)

After SPA validation, both the client and server authenticate each other using X.509 certificates. This bidirectional authentication prevents man-in-the-middle attacks and ensures both endpoints are verified.

Dynamic Provisioning

SDP connections are provisioned on-demand based on real-time policy evaluation. No persistent network tunnels exist; each session is individually authorized and encrypted.

Workflow

Phase 1: SDP Controller Deployment

  1. Deploy SDP Controller

    • Install SDP controller on hardened, redundant infrastructure
    • Configure PKI integration for certificate issuance
    • Set up authentication backend (LDAP, SAML, OIDC)
    • Configure policy database with application definitions
    • Enable audit logging for all controller decisions
  2. Configure Authentication

    • Integrate with enterprise IdP via SAML 2.0 or OIDC
    • Configure device certificate enrollment (SCEP/EST)
    • Enable multi-factor authentication requirements
    • Set up certificate revocation checking (OCSP/CRL)
  3. Define Access Policies

    • Map users/groups to authorized applications
    • Define device posture requirements per application
    • Configure contextual conditions (location, time, risk level)
    • Set session duration and re-authentication intervals

Phase 2: SDP Gateway Deployment

  1. Deploy Accepting Hosts (Gateways)

    • Install SDP gateway instances in front of protected applications
    • Configure default-drop firewall rules (deny all inbound)
    • Enable SPA listener on designated ports
    • Configure mTLS with controller-issued certificates
    • Set up health monitoring and failover
  2. Configure Application Definitions

    • Register each protected application with the controller
    • Define backend server IPs, ports, and protocols
    • Configure load balancing for multi-instance applications
    • Set up application health checks

Phase 3: Client Deployment

  1. Deploy Initiating Hosts (Clients)

    • Install SDP client software on user endpoints
    • Enroll device certificates through automated provisioning
    • Configure SPA key material distribution
    • Test authentication flow: SPA → mTLS → application access
  2. Validate End-to-End Flow

    • Verify SPA packets are accepted by gateway
    • Confirm mTLS handshake succeeds with valid certificates
    • Test application access through the SDP tunnel
    • Verify unauthorized access is blocked (no SPA = invisible gateway)

Phase 4: Operational Validation

  1. Security Testing

    • Port scan the SDP gateway to confirm invisibility (all ports show filtered/closed)
    • Attempt connection without valid SPA (must fail silently)
    • Test with revoked client certificate (must be denied)
    • Attempt lateral movement from one authorized app to another unauthorized app
    • Validate audit trail completeness
  2. Monitoring and Maintenance

    • Configure SIEM integration for SDP controller and gateway logs
    • Set up alerting for failed SPA attempts and certificate errors
    • Establish certificate rotation schedule
    • Document incident response procedures for SDP events

Validation Checklist

  • SDP Controller deployed with HA and audit logging
  • IdP integration tested with SAML/OIDC and MFA
  • SDP Gateways deployed with default-drop firewall
  • SPA mechanism validated (gateway invisible to port scans)
  • mTLS established between clients and gateways
  • Access policies enforce least-privilege per user/app
  • Device certificate enrollment automated
  • Unauthorized access attempts blocked silently
  • Lateral movement between apps prevented
  • Logs streaming to SIEM with alerting configured
  • Certificate rotation and revocation procedures tested

References

  • CSA Software-Defined Perimeter Architecture Guide v3
  • CSA SDP Specification v2.0
  • NIST SP 800-207: Zero Trust Architecture
  • CISA Zero Trust Maturity Model v2.0
  • fwknop: Single Packet Authorization implementation

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Assess exposure of Windows secrets protected by DPAPI, the operating system’s data protection service, during authorized security tests. Guide examination and decryption of saved credentials and browser data using available user sessions, credentials, or backup keys.

  • Assessing saved credential exposure in authorized tests
  • Examining collected DPAPI files offline
  • Reviewing protected browser and RDP credentials
mukul975/Anthropic-Cybersecurity-Skills34.8KUpdated Aug 31, 2026

Assess Shadow Credentials account takeover during authorized Active Directory testing. Examine permissions that allow public key registration, validate authentication without a password reset, and document credential cleanup, detection opportunities, and access control changes needed for remediation.

  • Assessing risky permissions identified in BloodHound
  • Validating account takeover without resetting a password
  • Generating directory change records during security exercises
mukul975/Anthropic-Cybersecurity-Skills34.8KUpdated Aug 31, 2026

Prepare for CMMC Level 2, a cybersecurity certification for defense contractors. Define the systems handling controlled information, review security requirements, calculate the SPRS assessment score, and organize remediation plans and evidence into a readiness report.

  • Define the assessment scope for systems handling controlled information
  • Calculate an SPRS score and prioritize unmet security requirements
  • Prepare security plans, remediation milestones, and assessment evidence
mukul975/Anthropic-Cybersecurity-Skills34.8KUpdated Aug 31, 2026

Create disk images for investigations using dd or dcfldd on Linux. The workflow covers write protection, bit-for-bit copying, hash checks to verify integrity, and documentation of the acquisition process.

  • Preserving a suspect drive before investigation
  • Creating evidence copies of USB devices or memory cards
  • Verifying that a disk image matches its source
mukul975/Anthropic-Cybersecurity-Skills34.8KUpdated Aug 31, 2026

Review Active Directory permissions with ldap3, a Python library for directory queries. Identify excessive access granted to non-administrative accounts, explain potential privilege escalation paths, and produce a JSON report with affected objects and remediation recommendations.

  • Auditing excessive Active Directory permissions
  • Investigating privilege escalation paths from ordinary accounts
  • Reporting affected objects and permission remediation recommendations
mukul975/Anthropic-Cybersecurity-Skills34.8KUpdated Aug 31, 2026

Inspect suspicious Android APK files without running them. Analyze permissions, app components, suspicious code patterns, and network indicators, then produce a JSON risk report to support malware triage and detection rule development.

  • Triage suspicious APK files without running them
  • Inspect dangerous permission combinations and suspicious API calls
  • Extract network indicators for malware detection rules
mukul975/Anthropic-Cybersecurity-Skills34.8KUpdated Aug 31, 2026

See all skills by mukul975

Report a problem with this skill