[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HMBMJ6GT6ZTFKCPK6YHB75":3,"skill-same:01M6HMBMJ6GT6ZTFKCPK6YHB75":115},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6HMBMJ6GT6ZTFKCPK6YHB75","implementing-scim-provisioning-with-okta",null,"Implement automated user provisioning and deprovisioning using SCIM 2.0 protocol with Okta as the identity provider.","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-scim-provisioning-with-okta\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"implementing","with","implementing scim provisioning with okta","scim","okta","provisioning","lifecycle","as","provider","access","identity-management","cybersecurity","t1098","t1078","lifecycle-management","sso","protocol","pr","automation","implement","2026-11-10 10:12:30",false,"---\nname: implementing-scim-provisioning-with-okta\ndescription: Implement automated user provisioning and deprovisioning using SCIM 2.0 protocol with Okta as the identity provider.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- scim\n- okta\n- provisioning\n- identity-management\n- automation\n- sso\n- lifecycle-management\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\ncategory: implementing-scim-provisioning-with-okta\n---\n# Implementing SCIM Provisioning with Okta\n\n## Overview\n\nSCIM (System for Cross-domain Identity Management) is an open standard protocol (RFC 7644) that automates the exchange of user identity information between identity providers like Okta and service providers. This skill covers building a SCIM 2.0-compliant API endpoint and integrating it with Okta for automated user lifecycle management including provisioning, deprovisioning, profile updates, and group management.\n\n\n## When to Use\n\n- When deploying or configuring implementing scim provisioning with okta capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Okta tenant with admin access (Developer or Production)\n- Application with REST API capable of user management\n- TLS-secured endpoint (HTTPS required)\n- Okta API token or OAuth 2.0 client credentials\n- Python 3.9+ with Flask or FastAPI\n\n## Core Concepts\n\n### SCIM 2.0 Protocol\n\nSCIM defines a standard schema for representing users and groups via JSON, with a RESTful API for CRUD operations:\n\n| Operation | HTTP Method | Endpoint | Description |\n|-----------|-------------|----------|-------------|\n| Create User | POST | \u002Fscim\u002Fv2\u002FUsers | Provisions a new user account |\n| Read User | GET | \u002Fscim\u002Fv2\u002FUsers\u002F{id} | Retrieves user details |\n| Update User | PUT\u002FPATCH | \u002Fscim\u002Fv2\u002FUsers\u002F{id} | Modifies user attributes |\n| Delete User | DELETE | \u002Fscim\u002Fv2\u002FUsers\u002F{id} | Removes user account |\n| List Users | GET | \u002Fscim\u002Fv2\u002FUsers | Lists users with filtering |\n| Create Group | POST | \u002Fscim\u002Fv2\u002FGroups | Creates a group |\n| Manage Group | PATCH | \u002Fscim\u002Fv2\u002FGroups\u002F{id} | Add\u002Fremove group members |\n\n### Okta SCIM Integration Architecture\n\n```\nOkta (IdP) ──SCIM 2.0 over HTTPS──> SCIM Server ──> Application Database\n     │                                     │\n     ├── User Assignment                   ├── Create\u002FUpdate User\n     ├── User Unassignment                 ├── Deactivate User\n     ├── Profile Push                      ├── Sync Attributes\n     └── Group Push                        └── Manage Groups\n```\n\n### Required SCIM Endpoints\n\n1. **ServiceProviderConfig** (`\u002Fscim\u002Fv2\u002FServiceProviderConfig`): Advertises SCIM capabilities\n2. **ResourceTypes** (`\u002Fscim\u002Fv2\u002FResourceTypes`): Describes supported resource types\n3. **Schemas** (`\u002Fscim\u002Fv2\u002FSchemas`): Publishes the SCIM schema definitions\n4. **Users** (`\u002Fscim\u002Fv2\u002FUsers`): User lifecycle operations\n5. **Groups** (`\u002Fscim\u002Fv2\u002FGroups`): Group management operations\n\n## Workflow\n\n### Step 1: Build SCIM 2.0 API Server\n\nCreate a Flask-based SCIM server that implements the core endpoints. The server must handle:\n\n- **User CRUD**: Create, read, update, delete, and list users\n- **Filtering**: Support `eq` filter on `userName` (required by Okta)\n- **Pagination**: Return `startIndex`, `itemsPerPage`, and `totalResults`\n- **Authentication**: Bearer token validation on all endpoints\n\n```python\nfrom flask import Flask, request, jsonify\nimport uuid\nfrom datetime import datetime\n\napp = Flask(__name__)\n\n# Bearer token for Okta authentication\nSCIM_BEARER_TOKEN = \"your-secure-token-here\"\n\ndef require_auth(f):\n    def wrapper(*args, **kwargs):\n        auth = request.headers.get(\"Authorization\", \"\")\n        if not auth.startswith(\"Bearer \") or auth[7:] != SCIM_BEARER_TOKEN:\n            return jsonify({\"detail\": \"Unauthorized\"}), 401\n        return f(*args, **kwargs)\n    wrapper.__name__ = f.__name__\n    return wrapper\n\n@app.route(\"\u002Fscim\u002Fv2\u002FUsers\", methods=[\"POST\"])\n@require_auth\ndef create_user():\n    data = request.json\n    user_id = str(uuid.uuid4())\n    user = {\n        \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n        \"id\": user_id,\n        \"userName\": data.get(\"userName\"),\n        \"name\": data.get(\"name\", {}),\n        \"emails\": data.get(\"emails\", []),\n        \"active\": True,\n        \"meta\": {\n            \"resourceType\": \"User\",\n            \"created\": datetime.utcnow().isoformat() + \"Z\",\n            \"lastModified\": datetime.utcnow().isoformat() + \"Z\",\n            \"location\": f\"\u002Fscim\u002Fv2\u002FUsers\u002F{user_id}\"\n        }\n    }\n    # Persist user to database\n    return jsonify(user), 201\n\n@app.route(\"\u002Fscim\u002Fv2\u002FUsers\", methods=[\"GET\"])\n@require_auth\ndef list_users():\n    filter_param = request.args.get(\"filter\", \"\")\n    start_index = int(request.args.get(\"startIndex\", 1))\n    count = int(request.args.get(\"count\", 100))\n    # Parse filter: userName eq \"john@example.com\"\n    # Query database with filter\n    return jsonify({\n        \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:ListResponse\"],\n        \"totalResults\": 0,\n        \"startIndex\": start_index,\n        \"itemsPerPage\": count,\n        \"Resources\": []\n    })\n```\n\n### Step 2: Configure Okta Application\n\n1. **Create SCIM App Integration**:\n   - Navigate to Okta Admin Console > Applications > Create App Integration\n   - Select SWA or SAML 2.0 as sign-on method\n   - In the General tab, select SCIM for Provisioning\n\n2. **Configure SCIM Connection**:\n   - SCIM connector base URL: `https:\u002F\u002Fyour-app.com\u002Fscim\u002Fv2`\n   - Unique identifier field: `userName`\n   - Supported provisioning actions: Push New Users, Push Profile Updates, Push Groups\n   - Authentication Mode: HTTP Header (Bearer Token)\n\n3. **Enable Provisioning Features**:\n   - To App: Create Users, Update User Attributes, Deactivate Users\n   - Configure attribute mappings between Okta profile and SCIM schema\n\n### Step 3: Map Attributes\n\nMap Okta user profile attributes to your SCIM schema:\n\n| Okta Attribute | SCIM Attribute | Direction |\n|---------------|----------------|-----------|\n| login | userName | Okta -> App |\n| firstName | name.givenName | Okta -> App |\n| lastName | name.familyName | Okta -> App |\n| email | emails[type eq \"work\"].value | Okta -> App |\n| department | urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department | Okta -> App |\n\n### Step 4: Implement Error Handling\n\nSCIM specifies standard error response format:\n\n```json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:Error\"],\n  \"detail\": \"User already exists\",\n  \"status\": \"409\",\n  \"scimType\": \"uniqueness\"\n}\n```\n\nCommon error codes: 400 (Bad Request), 401 (Unauthorized), 404 (Not Found), 409 (Conflict), 500 (Internal Server Error).\n\n### Step 5: Test with Runscope\u002FOkta SCIM Validator\n\nOkta provides an automated SCIM test suite (via Runscope\u002FBlazeMeter) that validates your SCIM implementation against all required operations:\n\n1. Import the Okta SCIM 2.0 test suite from the OIN submission portal\n2. Configure the base URL and authentication token\n3. Run the full test suite covering user CRUD, filtering, and pagination\n4. Fix any failing tests before submitting to OIN\n\n## Validation Checklist\n\n- [ ] SCIM server accessible over HTTPS with valid TLS certificate\n- [ ] Bearer token authentication enforced on all endpoints\n- [ ] User creation returns 201 with full user representation\n- [ ] User search by `userName eq \"...\"` filter works correctly\n- [ ] Pagination parameters (`startIndex`, `count`) handled properly\n- [ ] User deactivation sets `active: false` (not hard delete)\n- [ ] PATCH operations support `add`, `replace`, `remove` ops\n- [ ] Group push creates and manages group memberships\n- [ ] Okta SCIM validator test suite passes all tests\n- [ ] Error responses conform to SCIM error schema\n\n## References\n\n- [SCIM 2.0 Protocol RFC 7644](https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7644)\n- [Okta SCIM Developer Guide](https:\u002F\u002Fdeveloper.okta.com\u002Fdocs\u002Fguides\u002Fscim-provisioning-integration-overview\u002Fmain\u002F)\n- [Build a SCIM API Service - Okta](https:\u002F\u002Fdeveloper.okta.com\u002Fdocs\u002Fguides\u002Fscim-provisioning-integration-prepare\u002Fmain\u002F)\n- [SCIM Core Schema RFC 7643](https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7643)\n","# Implementing SCIM Provisioning with Okta\n\n## Overview\n\nSCIM (System for Cross-domain Identity Management) is an open standard protocol (RFC 7644) that automates the exchange of user identity information between identity providers like Okta and service providers. This skill covers building a SCIM 2.0-compliant API endpoint and integrating it with Okta for automated user lifecycle management including provisioning, deprovisioning, profile updates, and group management.\n\n\n## When to Use\n\n- When deploying or configuring implementing scim provisioning with okta capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Okta tenant with admin access (Developer or Production)\n- Application with REST API capable of user management\n- TLS-secured endpoint (HTTPS required)\n- Okta API token or OAuth 2.0 client credentials\n- Python 3.9+ with Flask or FastAPI\n\n## Core Concepts\n\n### SCIM 2.0 Protocol\n\nSCIM defines a standard schema for representing users and groups via JSON, with a RESTful API for CRUD operations:\n\n| Operation | HTTP Method | Endpoint | Description |\n|-----------|-------------|----------|-------------|\n| Create User | POST | \u002Fscim\u002Fv2\u002FUsers | Provisions a new user account |\n| Read User | GET | \u002Fscim\u002Fv2\u002FUsers\u002F{id} | Retrieves user details |\n| Update User | PUT\u002FPATCH | \u002Fscim\u002Fv2\u002FUsers\u002F{id} | Modifies user attributes |\n| Delete User | DELETE | \u002Fscim\u002Fv2\u002FUsers\u002F{id} | Removes user account |\n| List Users | GET | \u002Fscim\u002Fv2\u002FUsers | Lists users with filtering |\n| Create Group | POST | \u002Fscim\u002Fv2\u002FGroups | Creates a group |\n| Manage Group | PATCH | \u002Fscim\u002Fv2\u002FGroups\u002F{id} | Add\u002Fremove group members |\n\n### Okta SCIM Integration Architecture\n\n```\nOkta (IdP) ──SCIM 2.0 over HTTPS──> SCIM Server ──> Application Database\n     │                                     │\n     ├── User Assignment                   ├── Create\u002FUpdate User\n     ├── User Unassignment                 ├── Deactivate User\n     ├── Profile Push                      ├── Sync Attributes\n     └── Group Push                        └── Manage Groups\n```\n\n### Required SCIM Endpoints\n\n1. **ServiceProviderConfig** (`\u002Fscim\u002Fv2\u002FServiceProviderConfig`): Advertises SCIM capabilities\n2. **ResourceTypes** (`\u002Fscim\u002Fv2\u002FResourceTypes`): Describes supported resource types\n3. **Schemas** (`\u002Fscim\u002Fv2\u002FSchemas`): Publishes the SCIM schema definitions\n4. **Users** (`\u002Fscim\u002Fv2\u002FUsers`): User lifecycle operations\n5. **Groups** (`\u002Fscim\u002Fv2\u002FGroups`): Group management operations\n\n## Workflow\n\n### Step 1: Build SCIM 2.0 API Server\n\nCreate a Flask-based SCIM server that implements the core endpoints. The server must handle:\n\n- **User CRUD**: Create, read, update, delete, and list users\n- **Filtering**: Support `eq` filter on `userName` (required by Okta)\n- **Pagination**: Return `startIndex`, `itemsPerPage`, and `totalResults`\n- **Authentication**: Bearer token validation on all endpoints\n\n```python\nfrom flask import Flask, request, jsonify\nimport uuid\nfrom datetime import datetime\n\napp = Flask(__name__)\n\n# Bearer token for Okta authentication\nSCIM_BEARER_TOKEN = \"your-secure-token-here\"\n\ndef require_auth(f):\n    def wrapper(*args, **kwargs):\n        auth = request.headers.get(\"Authorization\", \"\")\n        if not auth.startswith(\"Bearer \") or auth[7:] != SCIM_BEARER_TOKEN:\n            return jsonify({\"detail\": \"Unauthorized\"}), 401\n        return f(*args, **kwargs)\n    wrapper.__name__ = f.__name__\n    return wrapper\n\n@app.route(\"\u002Fscim\u002Fv2\u002FUsers\", methods=[\"POST\"])\n@require_auth\ndef create_user():\n    data = request.json\n    user_id = str(uuid.uuid4())\n    user = {\n        \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n        \"id\": user_id,\n        \"userName\": data.get(\"userName\"),\n        \"name\": data.get(\"name\", {}),\n        \"emails\": data.get(\"emails\", []),\n        \"active\": True,\n        \"meta\": {\n            \"resourceType\": \"User\",\n            \"created\": datetime.utcnow().isoformat() + \"Z\",\n            \"lastModified\": datetime.utcnow().isoformat() + \"Z\",\n            \"location\": f\"\u002Fscim\u002Fv2\u002FUsers\u002F{user_id}\"\n        }\n    }\n    # Persist user to database\n    return jsonify(user), 201\n\n@app.route(\"\u002Fscim\u002Fv2\u002FUsers\", methods=[\"GET\"])\n@require_auth\ndef list_users():\n    filter_param = request.args.get(\"filter\", \"\")\n    start_index = int(request.args.get(\"startIndex\", 1))\n    count = int(request.args.get(\"count\", 100))\n    # Parse filter: userName eq \"john@example.com\"\n    # Query database with filter\n    return jsonify({\n        \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:ListResponse\"],\n        \"totalResults\": 0,\n        \"startIndex\": start_index,\n        \"itemsPerPage\": count,\n        \"Resources\": []\n    })\n```\n\n### Step 2: Configure Okta Application\n\n1. **Create SCIM App Integration**:\n   - Navigate to Okta Admin Console > Applications > Create App Integration\n   - Select SWA or SAML 2.0 as sign-on method\n   - In the General tab, select SCIM for Provisioning\n\n2. **Configure SCIM Connection**:\n   - SCIM connector base URL: `https:\u002F\u002Fyour-app.com\u002Fscim\u002Fv2`\n   - Unique identifier field: `userName`\n   - Supported provisioning actions: Push New Users, Push Profile Updates, Push Groups\n   - Authentication Mode: HTTP Header (Bearer Token)\n\n3. **Enable Provisioning Features**:\n   - To App: Create Users, Update User Attributes, Deactivate Users\n   - Configure attribute mappings between Okta profile and SCIM schema\n\n### Step 3: Map Attributes\n\nMap Okta user profile attributes to your SCIM schema:\n\n| Okta Attribute | SCIM Attribute | Direction |\n|---------------|----------------|-----------|\n| login | userName | Okta -> App |\n| firstName | name.givenName | Okta -> App |\n| lastName | name.familyName | Okta -> App |\n| email | emails[type eq \"work\"].value | Okta -> App |\n| department | urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department | Okta -> App |\n\n### Step 4: Implement Error Handling\n\nSCIM specifies standard error response format:\n\n```json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:Error\"],\n  \"detail\": \"User already exists\",\n  \"status\": \"409\",\n  \"scimType\": \"uniqueness\"\n}\n```\n\nCommon error codes: 400 (Bad Request), 401 (Unauthorized), 404 (Not Found), 409 (Conflict), 500 (Internal Server Error).\n\n### Step 5: Test with Runscope\u002FOkta SCIM Validator\n\nOkta provides an automated SCIM test suite (via Runscope\u002FBlazeMeter) that validates your SCIM implementation against all required operations:\n\n1. Import the Okta SCIM 2.0 test suite from the OIN submission portal\n2. Configure the base URL and authentication token\n3. Run the full test suite covering user CRUD, filtering, and pagination\n4. Fix any failing tests before submitting to OIN\n\n## Validation Checklist\n\n- [ ] SCIM server accessible over HTTPS with valid TLS certificate\n- [ ] Bearer token authentication enforced on all endpoints\n- [ ] User creation returns 201 with full user representation\n- [ ] User search by `userName eq \"...\"` filter works correctly\n- [ ] Pagination parameters (`startIndex`, `count`) handled properly\n- [ ] User deactivation sets `active: false` (not hard delete)\n- [ ] PATCH operations support `add`, `replace`, `remove` ops\n- [ ] Group push creates and manages group memberships\n- [ ] Okta SCIM validator test suite passes all tests\n- [ ] Error responses conform to SCIM error schema\n\n## References\n\n- [SCIM 2.0 Protocol RFC 7644](https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7644)\n- [Okta SCIM Developer Guide](https:\u002F\u002Fdeveloper.okta.com\u002Fdocs\u002Fguides\u002Fscim-provisioning-integration-overview\u002Fmain\u002F)\n- [Build a SCIM API Service - Okta](https:\u002F\u002Fdeveloper.okta.com\u002Fdocs\u002Fguides\u002Fscim-provisioning-integration-prepare\u002Fmain\u002F)\n- [SCIM Core Schema RFC 7643](https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7643)\n",{"name":5,"tags":44,"author":45,"domain":30,"license":15,"version":46,"category":5,"nist_csf":47,"subdomain":52,"description":7,"mitre_attack":53},[22,23,24,29,37,34,33],"mahipal","1.0",[48,49,50,51],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[54,55,56,57],"T1078","T1110","T1556","T1098","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fimplementing-scim-provisioning-with-okta",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill implementing-scim-provisioning-with-okta",{"tool":72,"command":73},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill implementing-scim-provisioning-with-okta",{"tool":75,"command":76},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill implementing-scim-provisioning-with-okta","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-scim-provisioning-with-okta\u002FSKILL.md",true,[80,86,91,97,101,105,111],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"assets\u002Ftemplate.md","ASSET","资产文件",2541,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-scim-provisioning-with-okta\u002Fassets\u002Ftemplate.md",{"path":87,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-scim-provisioning-with-okta\u002FLICENSE",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fapi-reference.md","REFERENCE","参考文档",4722,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-scim-provisioning-with-okta\u002Freferences\u002Fapi-reference.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fstandards.md",2315,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-scim-provisioning-with-okta\u002Freferences\u002Fstandards.md",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fworkflows.md",2903,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-scim-provisioning-with-okta\u002Freferences\u002Fworkflows.md",{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"scripts\u002Fagent.py","SCRIPT","脚本",9251,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-scim-provisioning-with-okta\u002Fscripts\u002Fagent.py",{"path":112,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":113,"sourceHtmlUrl":114},"scripts\u002Fprocess.py",15669,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-scim-provisioning-with-okta\u002Fscripts\u002Fprocess.py",[116,146,171,194,210,231],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":127,"publishedAt":39},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[122],{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[128,129,130,131,132,133,30,134,135,136,137,138,139,32,140,141,142,143,144,145],"integrity","backup","recovery","validating backup integrity for recovery","for","testing","validate","verification","hash-verification","incident-response","ransomware","detection","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":39},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[153,154,155,156,20,30,157,158,159,160,161,162,163,164,165,166,167,168,169,170],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":39},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[178,179,143,30,180,181,182,32,140,183,184,185,186,187,188,189,190,191,192,193],"security","triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":39},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[178,201,202,179,143,20,30,203,181,137,204,205,32,140,206,184,166,207,208,209],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":216,"publishedAt":39},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[178,217,218,219,220,221,30,222,223,224,181,225,32,226,227,228,187,229,143,230],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review","cm","de",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":237,"publishedAt":39},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[238,239,240,241,30,242,243,244,245,246,247,226,248,249,229,250,230,251,252,253],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]