[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B8YPT0ZR2KCGS7H5XH3NBA":3,"skill-same:01M7B8YPT0ZR2KCGS7H5XH3NBA":123},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":69,"commitSha":70,"skillDirectory":71,"forksCount":13,"repositoryHtmlUrl":72,"repositoryHomepageUrl":6,"ownerHtmlUrl":73,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":74,"install":75,"resources":88},"01M7B8YPT0ZR2KCGS7H5XH3NBA","performing-service-account-credential-rotation",null,"Automates credential rotation for service accounts across Active Directory, cloud platforms, and application databases to eliminate stale secrets and reduce compromise risk. Use when rotating or automating rotation of service account passwords, API keys, or secrets stored in a vault.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-service-account-credential-rotation\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-service-account-credential-rotation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-service-account-credential-rotation\ndescription: Automates credential rotation for service accounts across Active Directory,\n  cloud platforms, and application databases to eliminate stale secrets and reduce\n  compromise risk. Use when rotating or automating rotation of service account passwords,\n  API keys, or secrets stored in a vault.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- service-accounts\n- credential-rotation\n- secrets-management\n- pam\n- automation\n- vault\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AA-01\n- PR.AA-02\n- PR.AA-05\n- PR.AA-06\nmitre_attack:\n- T1078\n- T1110\n- T1556\n- T1098\n- T1003\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - initial-access\n  - positioning\n  - stealth\n  techniques:\n  - id: F1006.001\n    name: 'Account Takeover: Exposed API Key'\n    tactic: initial-access\n    source: f3\n  - id: F1006.002\n    name: 'Account Takeover: Exposed Login Credential'\n    tactic: initial-access\n    source: f3\n  - id: T1110\n    name: Brute Force\n    tactic: initial-access\n    source: attack\n  - id: F1005\n    name: Account Manipulation\n    tactic: positioning\n    source: f3\n  - id: F1023\n    name: Device Fingerprint Spoofing\n    tactic: stealth\n    source: f3\n---\n\n# Performing Service Account Credential Rotation\n\n## Overview\n\nService accounts are non-human identities used by applications, daemons, CI\u002FCD pipelines, and automated processes to authenticate to systems and APIs. These accounts often have elevated privileges and their credentials (passwords, API keys, certificates, tokens) are frequently long-lived and shared across teams, making them prime targets for attackers. Credential rotation is the systematic process of replacing these secrets on a scheduled basis, propagating new credentials to all dependent systems, and verifying service continuity after rotation.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing service account credential rotation\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Inventory of all service accounts across AD, cloud, and applications\n- Secrets management platform (HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, or CyberArk)\n- Service dependency mapping (which services use which credentials)\n- Change management process for rotation windows\n- Monitoring for service health post-rotation\n\n## Core Concepts\n\n### Service Account Types\n\n| Type | Platform | Credential | Rotation Method |\n|------|----------|-----------|-----------------|\n| Active Directory Service Account | Windows\u002FAD | Password | gMSA (automatic) or PAM-managed |\n| AWS IAM User | AWS | Access Key\u002FSecret Key | AWS Secrets Manager rotation Lambda |\n| GCP Service Account | GCP | JSON key file | Key rotation via IAM API |\n| Azure Service Principal | Azure | Client secret\u002Fcertificate | Key Vault + rotation policy |\n| Database Service Account | SQL\u002FOracle\u002FPostgres | Password | Vault dynamic secrets |\n| API Key | SaaS applications | API token | Application-specific API |\n\n### Group Managed Service Accounts (gMSA)\n\nWindows gMSAs provide automatic password management by Active Directory:\n- AD automatically rotates the password every 30 days\n- Password is 240 bytes, cryptographically random\n- Multiple servers can use the same gMSA simultaneously\n- No administrator knows or manages the password\n- Eliminates manual rotation for Windows services\n\n### Rotation Architecture\n\n```\nSecrets Manager \u002F Vault\n        │\n        ├── Rotation Trigger (schedule or on-demand)\n        │\n        ├── Generate new credential\n        │\n        ├── Update credential at source (AD, cloud IAM, database)\n        │\n        ├── Update credential in all consumers:\n        │   ├── Application configuration\n        │   ├── CI\u002FCD pipeline secrets\n        │   ├── Kubernetes secrets\n        │   └── Other dependent services\n        │\n        ├── Verify service health\n        │   ├── Health check endpoints\n        │   ├── Authentication test\n        │   └── Functional smoke test\n        │\n        └── Revoke old credential (after grace period)\n```\n\n## Workflow\n\n### Step 1: Discover and Inventory Service Accounts\n\nEnumerate all service accounts and their dependencies:\n\n```powershell\n# Active Directory: Find all service accounts\nGet-ADServiceAccount -Filter * -Properties *\nGet-ADUser -Filter {ServicePrincipalName -ne \"$null\"} -Properties ServicePrincipalName,PasswordLastSet,LastLogonDate\n\n# Find accounts with passwords older than 90 days\n$threshold = (Get-Date).AddDays(-90)\nGet-ADUser -Filter {PasswordLastSet -lt $threshold -and Enabled -eq $true} -Properties PasswordLastSet,ServicePrincipalName |\n    Where-Object {$_.ServicePrincipalName} |\n    Select-Object Name, PasswordLastSet, ServicePrincipalName\n```\n\n### Step 2: Implement gMSA for Windows Services\n\n```powershell\n# Create KDS Root Key (one-time, domain-wide)\nAdd-KdsRootKey -EffectiveImmediately\n\n# Create the gMSA account\nNew-ADServiceAccount -Name \"svc-webapp-gmsa\" `\n    -DNSHostName \"svc-webapp-gmsa.corp.example.com\" `\n    -PrincipalsAllowedToRetrieveManagedPassword \"WebServerGroup\" `\n    -KerberosEncryptionType AES128,AES256\n\n# Install on target server\nInstall-ADServiceAccount -Identity \"svc-webapp-gmsa\"\n\n# Test the account\nTest-ADServiceAccount -Identity \"svc-webapp-gmsa\"\n\n# Configure IIS Application Pool to use gMSA\n# Set identity to: CORP\\svc-webapp-gmsa$\n```\n\n### Step 3: AWS Access Key Rotation with Secrets Manager\n\n```python\nimport boto3\nimport json\n\ndef rotate_iam_access_key(secret_arn, iam_username):\n    \"\"\"Rotate an IAM user's access key via Secrets Manager.\"\"\"\n    iam = boto3.client(\"iam\")\n    sm = boto3.client(\"secretsmanager\")\n\n    # Create new access key\n    new_key = iam.create_access_key(UserName=iam_username)\n    new_access_key = new_key[\"AccessKey\"][\"AccessKeyId\"]\n    new_secret_key = new_key[\"AccessKey\"][\"SecretAccessKey\"]\n\n    # Store new credentials in Secrets Manager\n    sm.put_secret_value(\n        SecretId=secret_arn,\n        SecretString=json.dumps({\n            \"accessKeyId\": new_access_key,\n            \"secretAccessKey\": new_secret_key,\n            \"username\": iam_username,\n        })\n    )\n\n    # List old access keys and deactivate them\n    keys = iam.list_access_keys(UserName=iam_username)\n    for key in keys[\"AccessKeyMetadata\"]:\n        if key[\"AccessKeyId\"] != new_access_key and key[\"Status\"] == \"Active\":\n            iam.update_access_key(\n                UserName=iam_username,\n                AccessKeyId=key[\"AccessKeyId\"],\n                Status=\"Inactive\"\n            )\n\n    return {\"new_key_id\": new_access_key, \"old_keys_deactivated\": True}\n```\n\n### Step 4: Database Credential Rotation with Vault\n\n```python\nimport hvac\n\ndef configure_vault_database_rotation(vault_url, vault_token, db_config):\n    \"\"\"Configure HashiCorp Vault for automatic database credential rotation.\"\"\"\n    client = hvac.Client(url=vault_url, token=vault_token)\n\n    # Enable database secrets engine\n    client.sys.enable_secrets_engine(\n        backend_type=\"database\",\n        path=\"database\"\n    )\n\n    # Configure database connection\n    client.secrets.database.configure(\n        name=db_config[\"name\"],\n        plugin_name=\"postgresql-database-plugin\",\n        connection_url=f\"postgresql:\u002F\u002F{{{{username}}}}:{{{{password}}}}@\"\n                       f\"{db_config['host']}:{db_config['port']}\u002F{db_config['database']}\",\n        allowed_roles=[db_config[\"role_name\"]],\n        username=db_config[\"admin_user\"],\n        password=db_config[\"admin_password\"],\n    )\n\n    # Create a role for dynamic credentials\n    client.secrets.database.create_role(\n        name=db_config[\"role_name\"],\n        db_name=db_config[\"name\"],\n        creation_statements=[\n            \"CREATE ROLE \\\"{{name}}\\\" WITH LOGIN PASSWORD '{{password}}' VALID UNTIL '{{expiration}}';\",\n            f\"GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO \\\"{{{{name}}}}\\\";\"\n        ],\n        default_ttl=\"1h\",\n        max_ttl=\"24h\",\n    )\n\n    return {\"status\": \"configured\", \"role\": db_config[\"role_name\"]}\n```\n\n### Step 5: Post-Rotation Verification\n\nAfter every rotation, verify service continuity:\n\n```python\nimport requests\nimport time\n\ndef verify_service_health(service_endpoints, max_retries=3, delay=10):\n    \"\"\"Check that services are healthy after credential rotation.\"\"\"\n    results = []\n    for endpoint in service_endpoints:\n        for attempt in range(max_retries):\n            try:\n                response = requests.get(\n                    endpoint[\"health_url\"],\n                    timeout=10,\n                    headers=endpoint.get(\"headers\", {})\n                )\n                healthy = response.status_code == 200\n                results.append({\n                    \"service\": endpoint[\"name\"],\n                    \"status\": \"healthy\" if healthy else f\"unhealthy ({response.status_code})\",\n                    \"attempt\": attempt + 1,\n                })\n                if healthy:\n                    break\n            except requests.RequestException as e:\n                results.append({\n                    \"service\": endpoint[\"name\"],\n                    \"status\": f\"error: {str(e)}\",\n                    \"attempt\": attempt + 1,\n                })\n            if attempt \u003C max_retries - 1:\n                time.sleep(delay)\n\n    return results\n```\n\n## Validation Checklist\n\n- [ ] Complete inventory of service accounts with dependency mapping\n- [ ] gMSA implemented for all eligible Windows service accounts\n- [ ] Cloud access keys rotated via secrets manager (AWS, GCP, Azure)\n- [ ] Database credentials managed via dynamic secrets (Vault) or rotation policy\n- [ ] Rotation schedule defined (30-90 days depending on risk level)\n- [ ] Post-rotation health checks automated\n- [ ] Alerting configured for rotation failures\n- [ ] Old credentials revoked after grace period\n- [ ] Rotation events logged and auditable\n- [ ] Rollback procedure documented and tested\n\n## References\n\n- [Google Cloud Service Account Key Rotation](https:\u002F\u002Fcloud.google.com\u002Fiam\u002Fdocs\u002Fkey-rotation)\n- [AWS Secrets Manager Rotation](https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecretsmanager\u002Flatest\u002Fuserguide\u002Frotating-secrets.html)\n- [Microsoft gMSA Documentation](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fwindows-server\u002Fsecurity\u002Fgroup-managed-service-accounts\u002Fgroup-managed-service-accounts-overview)\n- [HashiCorp Vault Database Secrets Engine](https:\u002F\u002Fdeveloper.hashicorp.com\u002Fvault\u002Fdocs\u002Fsecrets\u002Fdatabases)\n","# Performing Service Account Credential Rotation\n\n## Overview\n\nService accounts are non-human identities used by applications, daemons, CI\u002FCD pipelines, and automated processes to authenticate to systems and APIs. These accounts often have elevated privileges and their credentials (passwords, API keys, certificates, tokens) are frequently long-lived and shared across teams, making them prime targets for attackers. Credential rotation is the systematic process of replacing these secrets on a scheduled basis, propagating new credentials to all dependent systems, and verifying service continuity after rotation.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing service account credential rotation\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Inventory of all service accounts across AD, cloud, and applications\n- Secrets management platform (HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, or CyberArk)\n- Service dependency mapping (which services use which credentials)\n- Change management process for rotation windows\n- Monitoring for service health post-rotation\n\n## Core Concepts\n\n### Service Account Types\n\n| Type | Platform | Credential | Rotation Method |\n|------|----------|-----------|-----------------|\n| Active Directory Service Account | Windows\u002FAD | Password | gMSA (automatic) or PAM-managed |\n| AWS IAM User | AWS | Access Key\u002FSecret Key | AWS Secrets Manager rotation Lambda |\n| GCP Service Account | GCP | JSON key file | Key rotation via IAM API |\n| Azure Service Principal | Azure | Client secret\u002Fcertificate | Key Vault + rotation policy |\n| Database Service Account | SQL\u002FOracle\u002FPostgres | Password | Vault dynamic secrets |\n| API Key | SaaS applications | API token | Application-specific API |\n\n### Group Managed Service Accounts (gMSA)\n\nWindows gMSAs provide automatic password management by Active Directory:\n- AD automatically rotates the password every 30 days\n- Password is 240 bytes, cryptographically random\n- Multiple servers can use the same gMSA simultaneously\n- No administrator knows or manages the password\n- Eliminates manual rotation for Windows services\n\n### Rotation Architecture\n\n```\nSecrets Manager \u002F Vault\n        │\n        ├── Rotation Trigger (schedule or on-demand)\n        │\n        ├── Generate new credential\n        │\n        ├── Update credential at source (AD, cloud IAM, database)\n        │\n        ├── Update credential in all consumers:\n        │   ├── Application configuration\n        │   ├── CI\u002FCD pipeline secrets\n        │   ├── Kubernetes secrets\n        │   └── Other dependent services\n        │\n        ├── Verify service health\n        │   ├── Health check endpoints\n        │   ├── Authentication test\n        │   └── Functional smoke test\n        │\n        └── Revoke old credential (after grace period)\n```\n\n## Workflow\n\n### Step 1: Discover and Inventory Service Accounts\n\nEnumerate all service accounts and their dependencies:\n\n```powershell\n# Active Directory: Find all service accounts\nGet-ADServiceAccount -Filter * -Properties *\nGet-ADUser -Filter {ServicePrincipalName -ne \"$null\"} -Properties ServicePrincipalName,PasswordLastSet,LastLogonDate\n\n# Find accounts with passwords older than 90 days\n$threshold = (Get-Date).AddDays(-90)\nGet-ADUser -Filter {PasswordLastSet -lt $threshold -and Enabled -eq $true} -Properties PasswordLastSet,ServicePrincipalName |\n    Where-Object {$_.ServicePrincipalName} |\n    Select-Object Name, PasswordLastSet, ServicePrincipalName\n```\n\n### Step 2: Implement gMSA for Windows Services\n\n```powershell\n# Create KDS Root Key (one-time, domain-wide)\nAdd-KdsRootKey -EffectiveImmediately\n\n# Create the gMSA account\nNew-ADServiceAccount -Name \"svc-webapp-gmsa\" `\n    -DNSHostName \"svc-webapp-gmsa.corp.example.com\" `\n    -PrincipalsAllowedToRetrieveManagedPassword \"WebServerGroup\" `\n    -KerberosEncryptionType AES128,AES256\n\n# Install on target server\nInstall-ADServiceAccount -Identity \"svc-webapp-gmsa\"\n\n# Test the account\nTest-ADServiceAccount -Identity \"svc-webapp-gmsa\"\n\n# Configure IIS Application Pool to use gMSA\n# Set identity to: CORP\\svc-webapp-gmsa$\n```\n\n### Step 3: AWS Access Key Rotation with Secrets Manager\n\n```python\nimport boto3\nimport json\n\ndef rotate_iam_access_key(secret_arn, iam_username):\n    \"\"\"Rotate an IAM user's access key via Secrets Manager.\"\"\"\n    iam = boto3.client(\"iam\")\n    sm = boto3.client(\"secretsmanager\")\n\n    # Create new access key\n    new_key = iam.create_access_key(UserName=iam_username)\n    new_access_key = new_key[\"AccessKey\"][\"AccessKeyId\"]\n    new_secret_key = new_key[\"AccessKey\"][\"SecretAccessKey\"]\n\n    # Store new credentials in Secrets Manager\n    sm.put_secret_value(\n        SecretId=secret_arn,\n        SecretString=json.dumps({\n            \"accessKeyId\": new_access_key,\n            \"secretAccessKey\": new_secret_key,\n            \"username\": iam_username,\n        })\n    )\n\n    # List old access keys and deactivate them\n    keys = iam.list_access_keys(UserName=iam_username)\n    for key in keys[\"AccessKeyMetadata\"]:\n        if key[\"AccessKeyId\"] != new_access_key and key[\"Status\"] == \"Active\":\n            iam.update_access_key(\n                UserName=iam_username,\n                AccessKeyId=key[\"AccessKeyId\"],\n                Status=\"Inactive\"\n            )\n\n    return {\"new_key_id\": new_access_key, \"old_keys_deactivated\": True}\n```\n\n### Step 4: Database Credential Rotation with Vault\n\n```python\nimport hvac\n\ndef configure_vault_database_rotation(vault_url, vault_token, db_config):\n    \"\"\"Configure HashiCorp Vault for automatic database credential rotation.\"\"\"\n    client = hvac.Client(url=vault_url, token=vault_token)\n\n    # Enable database secrets engine\n    client.sys.enable_secrets_engine(\n        backend_type=\"database\",\n        path=\"database\"\n    )\n\n    # Configure database connection\n    client.secrets.database.configure(\n        name=db_config[\"name\"],\n        plugin_name=\"postgresql-database-plugin\",\n        connection_url=f\"postgresql:\u002F\u002F{{{{username}}}}:{{{{password}}}}@\"\n                       f\"{db_config['host']}:{db_config['port']}\u002F{db_config['database']}\",\n        allowed_roles=[db_config[\"role_name\"]],\n        username=db_config[\"admin_user\"],\n        password=db_config[\"admin_password\"],\n    )\n\n    # Create a role for dynamic credentials\n    client.secrets.database.create_role(\n        name=db_config[\"role_name\"],\n        db_name=db_config[\"name\"],\n        creation_statements=[\n            \"CREATE ROLE \\\"{{name}}\\\" WITH LOGIN PASSWORD '{{password}}' VALID UNTIL '{{expiration}}';\",\n            f\"GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO \\\"{{{{name}}}}\\\";\"\n        ],\n        default_ttl=\"1h\",\n        max_ttl=\"24h\",\n    )\n\n    return {\"status\": \"configured\", \"role\": db_config[\"role_name\"]}\n```\n\n### Step 5: Post-Rotation Verification\n\nAfter every rotation, verify service continuity:\n\n```python\nimport requests\nimport time\n\ndef verify_service_health(service_endpoints, max_retries=3, delay=10):\n    \"\"\"Check that services are healthy after credential rotation.\"\"\"\n    results = []\n    for endpoint in service_endpoints:\n        for attempt in range(max_retries):\n            try:\n                response = requests.get(\n                    endpoint[\"health_url\"],\n                    timeout=10,\n                    headers=endpoint.get(\"headers\", {})\n                )\n                healthy = response.status_code == 200\n                results.append({\n                    \"service\": endpoint[\"name\"],\n                    \"status\": \"healthy\" if healthy else f\"unhealthy ({response.status_code})\",\n                    \"attempt\": attempt + 1,\n                })\n                if healthy:\n                    break\n            except requests.RequestException as e:\n                results.append({\n                    \"service\": endpoint[\"name\"],\n                    \"status\": f\"error: {str(e)}\",\n                    \"attempt\": attempt + 1,\n                })\n            if attempt \u003C max_retries - 1:\n                time.sleep(delay)\n\n    return results\n```\n\n## Validation Checklist\n\n- [ ] Complete inventory of service accounts with dependency mapping\n- [ ] gMSA implemented for all eligible Windows service accounts\n- [ ] Cloud access keys rotated via secrets manager (AWS, GCP, Azure)\n- [ ] Database credentials managed via dynamic secrets (Vault) or rotation policy\n- [ ] Rotation schedule defined (30-90 days depending on risk level)\n- [ ] Post-rotation health checks automated\n- [ ] Alerting configured for rotation failures\n- [ ] Old credentials revoked after grace period\n- [ ] Rotation events logged and auditable\n- [ ] Rollback procedure documented and tested\n\n## References\n\n- [Google Cloud Service Account Key Rotation](https:\u002F\u002Fcloud.google.com\u002Fiam\u002Fdocs\u002Fkey-rotation)\n- [AWS Secrets Manager Rotation](https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecretsmanager\u002Flatest\u002Fuserguide\u002Frotating-secrets.html)\n- [Microsoft gMSA Documentation](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fwindows-server\u002Fsecurity\u002Fgroup-managed-service-accounts\u002Fgroup-managed-service-accounts-overview)\n- [HashiCorp Vault Database Secrets Engine](https:\u002F\u002Fdeveloper.hashicorp.com\u002Fvault\u002Fdocs\u002Fsecrets\u002Fdatabases)\n",{"name":5,"tags":24,"author":31,"domain":32,"license":14,"version":33,"mitre_f3":34,"nist_csf":58,"subdomain":63,"description":7,"mitre_attack":64},[25,26,27,28,29,30],"service-accounts","credential-rotation","secrets-management","pam","automation","vault","mahipal","cybersecurity","1.0",{"tactics":35,"version":39,"techniques":40},[36,37,38],"initial-access","positioning","stealth","1.1",[41,45,48,52,55],{"id":42,"name":43,"source":44,"tactic":36},"F1006.001","Account Takeover: Exposed API Key","f3",{"id":46,"name":47,"source":44,"tactic":36},"F1006.002","Account Takeover: Exposed Login Credential",{"id":49,"name":50,"source":51,"tactic":36},"T1110","Brute Force","attack",{"id":53,"name":54,"source":44,"tactic":37},"F1005","Account Manipulation",{"id":56,"name":57,"source":44,"tactic":38},"F1023","Device Fingerprint Spoofing",[59,60,61,62],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[65,49,66,67,68],"T1078","T1556","T1098","T1003","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-service-account-credential-rotation","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill performing-service-account-credential-rotation",{"tool":81,"command":82},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill performing-service-account-credential-rotation",{"tool":84,"command":85},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill performing-service-account-credential-rotation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-service-account-credential-rotation\u002FSKILL.md",true,[89,95,99,105,109,113,119],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"assets\u002Ftemplate.md","ASSET","资产文件",1087,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-service-account-credential-rotation\u002Fassets\u002Ftemplate.md",{"path":96,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fapi-reference.md","REFERENCE","参考文档",2376,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-service-account-credential-rotation\u002Freferences\u002Fapi-reference.md",{"path":106,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fstandards.md",1964,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-service-account-credential-rotation\u002Freferences\u002Fstandards.md",{"path":110,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fworkflows.md",3586,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-service-account-credential-rotation\u002Freferences\u002Fworkflows.md",{"path":114,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002Fagent.py","SCRIPT","脚本",7042,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-service-account-credential-rotation\u002Fscripts\u002Fagent.py",{"path":120,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002Fprocess.py",9976,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-service-account-credential-rotation\u002Fscripts\u002Fprocess.py",[124,132,139,146,153,160],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":128,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":128,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":128,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":128,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":128,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":128,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]