Agent skill

Implementing Delinea Secret Server For Pam

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

Implements Delinea Secret Server for privileged access management, covering secret vault configuration, role-based access policies, automated password rotation, session recording, and Active…

Apache-2.0Auto-check passedLegal & Compliance

Install Implementing Delinea Secret Server For Pam

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-delinea-secret-server-for-pam -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills implementing-delinea-secret-server-for-pam --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/implementing-delinea-secret-server-for-pam .claude/skills/implementing-delinea-secret-server-for-pam && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
implementing-delinea-secret-server-for-pam
GitHub stars
34k
Token cost
~4.3k tokens
SKILL.md length
631 words
Files
4 (incl. scripts, references)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0

At a glance

Implements Delinea Secret Server for privileged access management, covering secret vault configuration, role-based access policies, automated password rotation, session recording, and Active…

  • Works in 6 steps: Deploy Secret Server Infrastructure → Configure Secret Templates and Folder… → Configure Discovery and Account Onboarding → …
  • Centralizing privileged credential management
  • SKILL.md covers When to Use, Prerequisites, Workflow and Key Concepts, plus 3 more sections
  • Runs Python scripts from its folder; calls go, vault and ssh; reaches thy.center; needs SS_ADMIN_PASSWORD

What it does

Implementing Delinea Secret Server For Pam is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Implements Delinea Secret Server for privileged access management, covering secret vault configuration, role-based access policies, automated password rotation, session recording, and Active Directory/cloud integration. Use when centralizing privileged credential management, replacing spreadsheet-based secrets, automating password rotation, or meeting PAM compliance (SOX, PCI-DSS, HIPAA, NIST 800-53).

Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/api-reference.md` and `scripts/agent.py`).

It sits in Legal & Compliance, covering Healthcare and finance regulation, Red teaming and adversary simulation and Authorization and RBAC. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.

When your agent uses it

  • Centralizing privileged credential management
  • Replacing spreadsheet-based secrets
  • Automating password rotation
  • Meeting PAM compliance (SOX

Example prompts

  • “Use the implementing-delinea-secret-server-for-pam skill to implement Delinea Secret Server for privileged access management, covering secret vault…”
  • “/implementing-delinea-secret-server-for-pam”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Deploy Secret Server Infrastructure
  2. Configure Secret Templates and Folder Structure
  3. Configure Discovery and Account Onboarding
  4. Implement Password Rotation Policies
  5. Configure Session Recording and Monitoring
  6. Integrate with SIEM and Compliance Reporting

What it can do on your machine

Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • go
    • vault
    • ssh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • thy.center

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • SS_ADMIN_PASSWORD

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Implementing Delinea Secret Server For Pam loads about 4.3k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 631 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~4.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 631 words, ~4,277 tokens.

Download SKILL.mdSave it as .claude/skills/implementing-delinea-secret-server-for-pam/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
implementing-delinea-secret-server-for-pam
description
Implements Delinea Secret Server for privileged access management, covering secret vault configuration, role-based access policies, automated password rotation, session recording, and Active Directory/cloud integration. Use when centralizing privileged credential management, replacing spreadsheet-based secrets, automating password rotation, or meeting PAM compliance (SOX, PCI-DSS, HIPAA, NIST 800-53).
domain
cybersecurity
subdomain
identity-access-management
tags
PAM, Delinea, Secret-Server, privileged-access, password-vault, credential-management
version
1.0
author
mahipal
license
Apache-2.0
nist_csf
PR.AA-01, PR.AA-02, PR.AA-05, PR.AA-06
mitre_attack
T1078, T1110, T1556, T1098, T1003
mitre_f3.version
1.1
mitre_f3.tactics
reconnaissance, initial-access, positioning

Implementing Delinea Secret Server for PAM

When to Use

  • Organization needs centralized privileged credential management across hybrid infrastructure
  • Compliance requirements mandate privileged access controls (SOX, PCI-DSS, HIPAA, NIST 800-53)
  • Service accounts and shared credentials are stored in spreadsheets or plaintext files
  • Need to implement automated password rotation for privileged accounts
  • Require session recording and keystroke logging for privileged user activity
  • Migrating from manual PAM processes to an enterprise vault solution

Do not use for standard end-user password management; Delinea Secret Server is designed for privileged and shared account credential management requiring enterprise-grade controls.

Prerequisites

  • Delinea Secret Server license (On-Premises or Cloud)
  • Windows Server 2019/2022 for on-premises deployment with IIS and SQL Server
  • Active Directory service account with read permissions for discovery
  • SSL/TLS certificate for web interface encryption
  • Network connectivity to target systems for password rotation
  • PowerShell 5.1+ for automation scripts

Workflow

Step 1: Deploy Secret Server Infrastructure

Install and configure the Secret Server application server:

powershell
# Pre-installation checks for on-premises deployment
# Verify IIS is installed with required features
Import-Module ServerManager
Install-WindowsFeature Web-Server, Web-Asp-Net45, Web-Windows-Auth, Web-Mgmt-Console

# Verify SQL Server connectivity
$sqlConn = New-Object System.Data.SqlClient.SqlConnection
$sqlConn.ConnectionString = "Server=sql01.corp.local;Database=master;Integrated Security=True"
$sqlConn.Open()
Write-Host "SQL Server connection successful: $($sqlConn.ServerVersion)"
$sqlConn.Close()

# Create Secret Server database
Invoke-Sqlcmd -ServerInstance "sql01.corp.local" -Query @"
CREATE DATABASE SecretServer
GO
ALTER DATABASE SecretServer SET RECOVERY FULL
GO
"@

# Download and run Secret Server installer
# Navigate to https://thy.center/ss/link/SSDownload for latest version
# Run setup.exe and follow the installation wizard

# Post-installation: Configure application pool
Import-Module WebAdministration
Set-ItemProperty "IIS:\AppPools\SecretServer" -Name processModel.identityType -Value SpecificUser
Set-ItemProperty "IIS:\AppPools\SecretServer" -Name processModel.userName -Value "CORP\svc-secretserver"
Step 2: Configure Secret Templates and Folder Structure

Define secret templates and organize the vault hierarchy:

powershell
# Connect to Secret Server API
$baseUrl = "https://pam.corp.local/SecretServer"
$creds = @{
    username = "ss-admin"
    password = $env:SS_ADMIN_PASSWORD
    grant_type = "password"
}
$token = (Invoke-RestMethod "$baseUrl/oauth2/token" -Method POST -Body $creds).access_token
$headers = @{ Authorization = "Bearer $token" }

# Create folder structure for organizing secrets
$folders = @(
    @{ folderName = "Windows Servers"; parentFolderId = -1; inheritPermissions = $false },
    @{ folderName = "Linux Servers"; parentFolderId = -1; inheritPermissions = $false },
    @{ folderName = "Network Devices"; parentFolderId = -1; inheritPermissions = $false },
    @{ folderName = "Cloud Accounts"; parentFolderId = -1; inheritPermissions = $false },
    @{ folderName = "Service Accounts"; parentFolderId = -1; inheritPermissions = $false },
    @{ folderName = "Database Accounts"; parentFolderId = -1; inheritPermissions = $false }
)

foreach ($folder in $folders) {
    Invoke-RestMethod "$baseUrl/api/v1/folders" -Method POST -Headers $headers `
        -ContentType "application/json" -Body ($folder | ConvertTo-Json)
}

# Create custom secret template for database credentials
$template = @{
    name = "Database Credential"
    fields = @(
        @{ name = "Server"; isRequired = $true; fieldType = "Text" },
        @{ name = "Port"; isRequired = $true; fieldType = "Text" },
        @{ name = "Database"; isRequired = $true; fieldType = "Text" },
        @{ name = "Username"; isRequired = $true; fieldType = "Text" },
        @{ name = "Password"; isRequired = $true; fieldType = "Password" },
        @{ name = "Connection String"; isRequired = $false; fieldType = "Notes" }
    )
}
Invoke-RestMethod "$baseUrl/api/v1/secret-templates" -Method POST -Headers $headers `
    -ContentType "application/json" -Body ($template | ConvertTo-Json -Depth 3)
Step 3: Configure Discovery and Account Onboarding

Set up automated discovery of privileged accounts across the environment:

powershell
# Configure Active Directory discovery source
$adDiscovery = @{
    name = "Corporate AD Discovery"
    discoverySourceType = "ActiveDirectory"
    active = $true
    settings = @{
        domainName = "corp.local"
        friendlyName = "Corporate Domain"
        discoveryAccountId = 12  # Service account secret ID
        ouFilters = @(
            "OU=Servers,DC=corp,DC=local",
            "OU=Workstations,DC=corp,DC=local"
        )
    }
    scanInterval = 86400  # 24 hours
}
Invoke-RestMethod "$baseUrl/api/v1/discovery" -Method POST -Headers $headers `
    -ContentType "application/json" -Body ($adDiscovery | ConvertTo-Json -Depth 3)

# Configure local account discovery for Windows servers
$localDiscovery = @{
    name = "Windows Local Account Discovery"
    discoverySourceType = "Machine"
    active = $true
    settings = @{
        machineType = "Windows"
        accountScanTemplate = "Windows Local Account"
        dependencyScanTemplate = "Windows Service"
    }
}
Invoke-RestMethod "$baseUrl/api/v1/discovery" -Method POST -Headers $headers `
    -ContentType "application/json" -Body ($localDiscovery | ConvertTo-Json -Depth 3)

# Import discovered accounts as secrets
# After discovery runs, review and import found accounts
$discoveredAccounts = Invoke-RestMethod "$baseUrl/api/v1/discovery/status" -Headers $headers
Write-Host "Discovered $($discoveredAccounts.totalAccounts) accounts"
Write-Host "  - Domain Admins: $($discoveredAccounts.domainAdmins)"
Write-Host "  - Local Admins: $($discoveredAccounts.localAdmins)"
Write-Host "  - Service Accounts: $($discoveredAccounts.serviceAccounts)"
Step 4: Implement Password Rotation Policies

Configure automated password rotation with complexity requirements:

powershell
# Create password rotation policy
$rotationPolicy = @{
    name = "High-Security 30-Day Rotation"
    rotationIntervalDays = 30
    passwordRequirements = @{
        minimumLength = 24
        maximumLength = 32
        requireUpperCase = $true
        requireLowerCase = $true
        requireNumbers = $true
        requireSymbols = $true
        allowedSymbols = "!@#$%^&*()-_=+[]{}|;:,.<>?"
    }
    rotationType = "AutoChange"
    autoChangeSchedule = @{
        changeType = "RecurringSchedule"
        recurrenceType = "Monthly"
        dayOfMonth = 1
        startTime = "02:00"
    }
}
Invoke-RestMethod "$baseUrl/api/v1/remote-password-changing/configuration" -Method POST `
    -Headers $headers -ContentType "application/json" -Body ($rotationPolicy | ConvertTo-Json -Depth 4)

# Configure Remote Password Changing (RPC) for Windows accounts
$rpcConfig = @{
    secretId = 100  # Target secret
    autoChangeEnabled = $true
    autoChangeNextPassword = $true
    privilegedAccountSecretId = 50  # Account used to perform the change
    changePasswordUsing = "PrivilegedAccount"
}
Invoke-RestMethod "$baseUrl/api/v1/secrets/100/remote-password-changing" -Method PUT `
    -Headers $headers -ContentType "application/json" -Body ($rpcConfig | ConvertTo-Json)

# Configure heartbeat monitoring to verify credential validity
$heartbeat = @{
    enabled = $true
    intervalMinutes = 60
    onFailure = "SendAlert"
    alertEmailGroupId = 5
}
Invoke-RestMethod "$baseUrl/api/v1/secrets/100/heartbeat" -Method PUT `
    -Headers $headers -ContentType "application/json" -Body ($heartbeat | ConvertTo-Json)
Step 5: Configure Session Recording and Monitoring

Enable session recording for privileged access sessions:

powershell
# Enable session recording policy
$sessionPolicy = @{
    name = "Full Recording Policy"
    recordSessions = $true
    recordKeystrokes = $true
    recordApplications = $true
    maxSessionDurationMinutes = 480
    requireComment = $true
    requireTicketNumber = $true
    ticketSystemId = 1  # ServiceNow integration
    settings = @{
        videoCodec = "H264"
        videoQuality = "High"
        captureInterval = 1000  # milliseconds
        storageLocation = "\\\\fileserver\\SSRecordings"
        retentionDays = 365
    }
}
Invoke-RestMethod "$baseUrl/api/v1/secret-policy" -Method POST -Headers $headers `
    -ContentType "application/json" -Body ($sessionPolicy | ConvertTo-Json -Depth 3)

# Configure session launcher for RDP sessions
$rdpLauncher = @{
    launcherType = "RDP"
    enableRecording = $true
    enableDualControl = $true
    approverGroupId = 10  # Security team group
    connectAsSecretId = 100
    settings = @{
        useSSL = $true
        restrictedEndpoints = @("192.168.1.0/24")
        inactivityTimeout = 30  # minutes
    }
}
Invoke-RestMethod "$baseUrl/api/v1/launchers" -Method POST -Headers $headers `
    -ContentType "application/json" -Body ($rdpLauncher | ConvertTo-Json -Depth 3)

# Configure dual control / approval workflow
$approvalWorkflow = @{
    name = "Tier-0 Account Approval"
    requireApproval = $true
    approvers = @(
        @{ groupId = 10; requiredApprovals = 1 }
    )
    accessRequestExpirationMinutes = 60
    notifyOnApproval = $true
    notifyOnDenial = $true
}
Step 6: Integrate with SIEM and Compliance Reporting

Connect Secret Server events to security monitoring:

powershell
# Configure Syslog forwarding to SIEM
$syslogConfig = @{
    enabled = $true
    syslogServer = "siem.corp.local"
    port = 514
    protocol = "TLS"
    facility = "Auth"
    severity = "Informational"
    events = @(
        "SecretView", "SecretEdit", "SecretCreate", "SecretDelete",
        "PasswordChange", "PasswordChangeFailure",
        "SessionStart", "SessionEnd",
        "LoginFailure", "LoginSuccess",
        "PermissionChange", "ApprovalRequest"
    )
}
Invoke-RestMethod "$baseUrl/api/v1/configuration/syslog" -Method PUT -Headers $headers `
    -ContentType "application/json" -Body ($syslogConfig | ConvertTo-Json -Depth 2)

# Generate compliance report
$report = @{
    reportType = "PasswordCompliance"
    dateRange = @{
        startDate = (Get-Date).AddDays(-30).ToString("yyyy-MM-dd")
        endDate = (Get-Date).ToString("yyyy-MM-dd")
    }
    filters = @{
        folderIds = @(1, 2, 3, 4, 5, 6)
        includeSubFolders = $true
    }
}
$reportResult = Invoke-RestMethod "$baseUrl/api/v1/reports" -Method POST -Headers $headers `
    -ContentType "application/json" -Body ($report | ConvertTo-Json -Depth 3)

# Display compliance summary
Write-Host "PAM Compliance Report"
Write-Host "====================="
Write-Host "Total Secrets:         $($reportResult.totalSecrets)"
Write-Host "Rotation Compliant:    $($reportResult.rotationCompliant) ($($reportResult.rotationCompliancePct)%)"
Write-Host "Heartbeat Healthy:     $($reportResult.heartbeatHealthy) ($($reportResult.heartbeatHealthyPct)%)"
Write-Host "Password Age > 90d:    $($reportResult.passwordAgeViolations)"
Write-Host "Orphaned Accounts:     $($reportResult.orphanedAccounts)"

Key Concepts

TermDefinition
Privileged Access Management (PAM)Security framework for controlling, monitoring, and auditing elevated access to critical systems and data through credential vaulting and session management
SecretA stored credential or sensitive data item in the vault, including passwords, SSH keys, API tokens, and certificates
Remote Password Changing (RPC)Automated mechanism that connects to target systems to rotate passwords according to defined policies without manual intervention
HeartbeatPeriodic check that validates stored credentials against target systems to ensure vault contents remain synchronized and functional
Dual ControlSecurity mechanism requiring approval from a second authorized user before granting access to highly sensitive secrets
DiscoveryAutomated scanning of infrastructure to identify privileged accounts, service accounts, and dependencies across Active Directory, servers, and network devices
Session RecordingCapture of complete privileged session activity including video, keystrokes, and application usage for audit and forensic review
Show full SKILL.md (258 more words)Show less

Tools & Systems

  • Delinea Secret Server: Enterprise PAM solution providing credential vaulting, password rotation, session recording, and privileged access workflows
  • Delinea Distributed Engine: Agent deployed in network segments to enable password changing and discovery across firewalled environments
  • Secret Server REST API: RESTful API for programmatic secret management, automation, and integration with DevOps pipelines
  • Secret Server SDK: .NET and PowerShell SDKs for application-level integration with Secret Server vault

Common Scenarios

Scenario: Migrating Shared Admin Credentials to Vault

Context: An organization stores 500+ shared administrator credentials in Excel spreadsheets and password-protected documents. Auditors flagged this as a critical finding requiring remediation within 90 days.

Approach:

  1. Deploy Secret Server with SQL Server backend and configure HTTPS access
  2. Design folder hierarchy mirroring the organizational structure (by department, system type, environment)
  3. Create secret templates matching the credential types in use (Windows, Linux, database, network device)
  4. Import existing credentials via CSV import or PowerShell bulk creation
  5. Configure discovery to find undocumented privileged accounts across AD and local systems
  6. Enable Remote Password Changing starting with non-production accounts to validate rotation
  7. Roll out session launchers to replace direct RDP/SSH connections
  8. Gradually enable dual control for Tier-0 accounts (Domain Admins, root accounts)
  9. Configure SIEM integration and compliance reporting for audit evidence

Pitfalls:

  • Not identifying all service account dependencies before enabling password rotation (causes service outages)
  • Enabling RPC for production accounts without testing in non-production first
  • Setting rotation intervals too short for service accounts that require coordinated restarts
  • Not configuring Distributed Engines for network segments separated by firewalls

Output Format

DELINEA SECRET SERVER PAM DEPLOYMENT REPORT
=============================================
Environment:       Hybrid (On-Premises + Azure)
Version:           Secret Server 11.6
Deployment Mode:   On-Premises (High Availability)

VAULT STATISTICS
Total Secrets:           1,247
  Windows Credentials:   523
  Linux/SSH Keys:        312
  Database Accounts:     198
  Network Devices:       87
  Cloud API Keys:        127

PASSWORD ROTATION STATUS
Auto-Change Enabled:     1,089 / 1,247 (87.3%)
Rotation Compliant:      1,056 / 1,089 (97.0%)
Heartbeat Healthy:       1,198 / 1,247 (96.1%)
Failed Rotations (30d):  12

SESSION MANAGEMENT
Active Sessions:         23
Recorded Sessions (30d): 4,567
Average Session Length:  22 minutes
Approval Requests (30d): 189 (174 approved, 15 denied)

DISCOVERY RESULTS
Scanned Systems:         2,340
Discovered Accounts:     3,891
Onboarded to Vault:      1,247 (32.1%)
Pending Review:          892

COMPLIANCE
SOX Controls Met:        12/12
PCI-DSS Requirements:    8/8
Password Age Violations: 3 (remediation in progress)

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in skills/implementing-delinea-secret-server-for-pam of mukul975/Anthropic-Cybersecurity-Skills.

  • SKILL.md
  • LICENSE
  • references/api-reference.md
  • scripts/agent.py

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Implementing Delinea Secret Server For Pam next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Implementing Delinea Secret Server For Pam compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Implementing Delinea Secret Server For Pam this skillmukul975/Anthropic-Cybersecurity-Skills34k—~4.3kAutomated safety check: PassApache-2.0
Healthcare Phi Complianceaffaan-m/ECC276k1 repos~1.4kAutomated safety check: PassMIT
Policy OpaAgentSecOps/SecOpsAgentKit2201 repos~3.5kAutomated safety check: PassCustom licence
Hipaa Employee Trainingmukul975/Privacy-Data-Protection-Skills301—~1.9kAutomated safety check: PassApache-2.0
Hipaa Research Privacymukul975/Privacy-Data-Protection-Skills301—~1.7kAutomated safety check: PassApache-2.0
HealthclawLeoYeAI/openclaw-master-skills2.2k—~4.9kAutomated safety check: PassMIT

Similar skills

  • Protected Health Information (PHI) and PII compliance patterns for healthcare applications: data classification, row-level access control, tamper-proof audit trails, schema tagging, and common leak…

    276k GitHub starsUsed in 1 repo~1.4k tokens
    Legal & ComplianceAuto-check passed
  • Policy Opa

    AgentSecOps/SecOpsAgentKit

    Policy-as-code enforcement and compliance validation using Open Policy Agent (OPA).

    220 GitHub starsUsed in 1 repo~3.5k tokens
    Legal & ComplianceAuto-check passed
  • Hipaa Employee Training

    mukul975/Privacy-Data-Protection-Skills

    Implements HIPAA workforce training requirements under 45 CFR §164.530(b) (Privacy Rule) and 45 CFR §164.308(a)(5) (Security Rule).

    301 GitHub stars~1.9k tokensUpdated 6 mo ago
    Legal & ComplianceAuto-check passed
  • Hipaa Research Privacy

    mukul975/Privacy-Data-Protection-Skills

    Implements HIPAA Privacy Rule requirements for research uses of protected health information under 45 CFR §164.512(i).

    301 GitHub stars~1.7k tokensUpdated 6 mo ago
    Legal & ComplianceAuto-check passed
  • Healthclaw

    LeoYeAI/openclaw-master-skills

    AI-native hospital and multi-department healthcare ERP. An agent skill from LeoYeAI/openclaw-master-skills.

    2.2k GitHub stars~4.9k tokensUpdated 2 mo ago
    Legal & ComplianceAuto-check passed
  • Ise Posture Audit

    automateyournetwork/netclaw

    Cisco ISE posture and policy audit - authorization rules, posture compliance, profiling gaps, TrustSec SGT matrix, active session health.

    676 GitHub stars~3k tokensUpdated today
    Legal & ComplianceAuto-check passed

More from mukul975/Anthropic-Cybersecurity-Skills

All 644 skills in this repo
  • Campaign Attribution Evidence Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Go Malware Analysis in Ghidra

    mukul975/Anthropic-Cybersecurity-Skills

    Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • LNK and Jump List Forensics

    mukul975/Anthropic-Cybersecurity-Skills

    Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Malware Persistence Analysis with Autoruns

    mukul975/Anthropic-Cybersecurity-Skills

    Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • NTFS MFT Deleted File Recovery

    mukul975/Anthropic-Cybersecurity-Skills

    Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Network Covert Channel Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Implementing Delinea Secret Server For Pam

What does Implementing Delinea Secret Server For Pam do?

Implements Delinea Secret Server for privileged access management, covering secret vault configuration, role-based access policies, automated password rotation, session recording, and Active…. Implementing Delinea Secret Server For Pam is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Implements Delinea Secret Server for privileged access management, covering secret vault configuration, role-based access policies, automated password rotation, session recording, and Active Directory/cloud integration.

When should I use Implementing Delinea Secret Server For Pam?

Implementing Delinea Secret Server For Pam fits situations like: centralizing privileged credential management; replacing spreadsheet-based secrets; automating password rotation; meeting PAM compliance (SOX.

How do I install Implementing Delinea Secret Server For Pam in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-delinea-secret-server-for-pam -a claude-code`. Or copy the skill folder (skills/implementing-delinea-secret-server-for-pam in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/implementing-delinea-secret-server-for-pam in your project. Claude Code loads it when a task matches its description.

How do I install Implementing Delinea Secret Server For Pam in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-delinea-secret-server-for-pam -a codex`. Or copy the skill folder (skills/implementing-delinea-secret-server-for-pam in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/implementing-delinea-secret-server-for-pam in your project. Codex loads it when a task matches its description.

Can I use Implementing Delinea Secret Server For Pam in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-delinea-secret-server-for-pam -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implementing-delinea-secret-server-for-pam, .gemini/skills/implementing-delinea-secret-server-for-pam, .github/skills/implementing-delinea-secret-server-for-pam and .opencode/skills/implementing-delinea-secret-server-for-pam in your project.

What does Implementing Delinea Secret Server For Pam need to run?

Going by SKILL.md and its folder, Implementing Delinea Secret Server For Pam needs Python for the scripts in its folder, the command-line tools its instructions call (go, vault and ssh) and credentials named SS_ADMIN_PASSWORD. Our summary lists: Python 3.

Does Implementing Delinea Secret Server For Pam access the network?

SKILL.md names 1 domain. In commands or code: thy.center; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Implementing Delinea Secret Server For Pam safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Implementing Delinea Secret Server For Pam use?

Implementing Delinea Secret Server For Pam is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Implementing Delinea Secret Server For Pam use?

About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 583 tokens, read only when the agent opens those files.

What are the alternatives to Implementing Delinea Secret Server For Pam?

Skills that share tags, products or a category with Implementing Delinea Secret Server For Pam: Healthcare Phi Compliance (affaan-m/ECC, 276k stars), Policy Opa (AgentSecOps/SecOpsAgentKit, 220 stars), Hipaa Employee Training (mukul975/Privacy-Data-Protection-Skills, 301 stars) and Hipaa Research Privacy (mukul975/Privacy-Data-Protection-Skills, 301 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Implementing Delinea Secret Server For Pam?

mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.

Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.