[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71CBTP0TS1XJMYKBT4J2JXY":3,"skill-same:01M71CBTP0TS1XJMYKBT4J2JXY":60},{"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":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":14,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M71CBTP0TS1XJMYKBT4J2JXY","cloud-zerotrust-zscaler-zia",null,"- CSA Software-Defined Perimeter and Zero Trust Specification v2.","DCx7C5\u002Fai-marketplace","DCx7C5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42419559?v=4","01M71C01G2AZV3NTNGWAWSHJPP","DC","01M71C01GQW6G50S2BYMS7PP3E",0,"MIT","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud-zerotrust-zscaler-zia\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"zscaler","cloud","cloud zerotrust zscaler zia","trust","ZeRO","cybersecurity","specification","software","zero trust","2026-11-10 10:12:30",false,"---\nname: cloud-zerotrust-zscaler-zia\ndescription: \"- CSA Software-Defined Perimeter and Zero Trust Specification v2.\"\ndomain: cybersecurity\n---\n\n# Implementing Zero Trust Network Access with Zscaler\n\n## Prerequisites\n\n- Understanding of zero trust principles (NIST SP 800-207)\n- Familiarity with identity providers (Okta, Azure AD, Ping Identity)\n- Knowledge of network security fundamentals\n- Access to Zscaler Private Access (ZPA) tenant\n\n## Overview\n\nZero Trust Network Access (ZTNA) replaces traditional VPN architectures by enforcing identity-based, context-aware access to private applications without placing users on the corporate network. Zscaler Private Access (ZPA) is a leading ZTNA solution that brokers secure connections between authenticated users and internal applications through the Zscaler Zero Trust Exchange cloud platform.\n\nThis skill covers end-to-end deployment of ZPA including connector setup, application segmentation, policy configuration, and integration with identity providers for continuous verification.\n\n## When to Use\n\n- When deploying or configuring implementing zero trust network access with zscaler 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- Familiarity with zero trust architecture concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Architecture\n\n### Zscaler Private Access Components\n\n1. **Client Connector**: Lightweight agent on user endpoints that establishes outbound TLS tunnels to the nearest ZPA Service Edge\n2. **ZPA Service Edge**: Cloud-hosted broker (or Private Service Edge on-premises) that stitches user-to-app connections after policy evaluation\n3. **App Connector**: Lightweight VM deployed in the application environment that creates outbound tunnels to the Service Edge\n4. **ZPA Admin Portal**: Centralized management console for defining applications, segments, and access policies\n\n### Connection Flow\n\n```\nUser Device (Client Connector)\n    |\n    v [Outbound TLS tunnel]\nZPA Service Edge (Policy Evaluation + IdP Auth)\n    |\n    v [Outbound TLS tunnel]\nApp Connector --> Internal Application\n```\n\nKey principle: No inbound connections are required. Both the Client Connector and App Connector initiate outbound-only connections, eliminating the attack surface of traditional VPNs.\n\n## Key Concepts\n\n### Application Segments\nDefine specific applications or groups of applications by IP address, FQDN, port, and protocol. Segments enable granular microsegmentation rather than broad network access.\n\n### Access Policies\nPolicies combine user identity, group membership, device posture, and contextual signals (location, time) to grant or deny access to application segments.\n\n### Server Groups\nLogical groupings of App Connectors that serve specific application segments, enabling high availability and geographic distribution.\n\n### Browser Access\nZPA supports clientless browser-based access for web applications, enabling ZTNA for unmanaged devices and third-party users without requiring the Client Connector.\n\n## Workflow\n\n### Phase 1: Foundation Setup\n\n1. **Configure Identity Provider Integration**\n   - Navigate to Administration > IdP Configuration in ZPA Admin Portal\n   - Add SAML 2.0 or OIDC integration with your IdP (Azure AD, Okta, Ping)\n   - Configure SCIM provisioning for automatic user\u002Fgroup synchronization\n   - Test SSO authentication flow\n\n2. **Deploy App Connectors**\n   - Provision App Connector VMs in each application environment (data center, AWS VPC, Azure VNet)\n   - Download the provisioning key from ZPA Admin Portal\n   - Install and enroll the App Connector using the provisioning key\n   - Verify connector status shows \"Healthy\" in the admin portal\n   - Deploy at least two connectors per environment for high availability\n\n3. **Create Server Groups**\n   - Group App Connectors by geographic location or application tier\n   - Configure health check intervals and failover behavior\n\n### Phase 2: Application Segmentation\n\n4. **Define Application Segments**\n   - Create segments for each application or logical group\n   - Specify domains\u002FIPs, ports, and protocols\n   - Associate segments with appropriate server groups\n   - Enable or disable browser access as needed\n\n5. **Create Segment Groups**\n   - Organize application segments into logical groups (e.g., HR apps, Finance apps)\n   - Use segment groups to simplify policy management\n\n### Phase 3: Policy Configuration\n\n6. **Configure Access Policies**\n   - Define rules matching user groups to application segments\n   - Apply conditions: device posture, client type, SAML attributes\n   - Order rules by priority (most restrictive first)\n   - Create deny rules for blocked access scenarios\n\n7. **Enable Device Posture Checks**\n   - Configure posture profiles requiring OS patch level, disk encryption, antivirus status\n   - Integrate with endpoint management (CrowdStrike, Microsoft Intune, Carbon Black)\n   - Associate posture profiles with access policies\n\n### Phase 4: Client Deployment\n\n8. **Deploy Client Connector**\n   - Package the Zscaler Client Connector with enrollment token\n   - Deploy via MDM (Intune, Jamf, SCCM) or manual installation\n   - Configure forwarding profile to route private app traffic through ZPA\n   - Test user authentication and application access\n\n### Phase 5: Monitoring and Optimization\n\n9. **Enable Logging and Monitoring**\n   - Configure log streaming to SIEM (Splunk, Sentinel, QRadar)\n   - Set up alerts for policy violations, connector health, and authentication failures\n   - Review ZPA Insights dashboard for usage analytics\n\n10. **Iterative Refinement**\n    - Analyze access logs to identify shadow IT and unauthorized access attempts\n    - Refine application segments based on actual traffic patterns\n    - Expand coverage from pilot applications to full enterprise deployment\n\n## Validation Checklist\n\n- [ ] Identity provider integration tested with SSO and SCIM sync\n- [ ] App Connectors deployed and showing healthy status in all environments\n- [ ] Application segments defined with correct IPs\u002FFQDNs, ports, protocols\n- [ ] Access policies enforce least-privilege per user group\n- [ ] Device posture checks block non-compliant endpoints\n- [ ] Client Connector deployed to all managed endpoints\n- [ ] Log streaming to SIEM confirmed with test events\n- [ ] Failover tested by disabling one App Connector per server group\n- [ ] Browser Access configured for web apps requiring third-party access\n- [ ] VPN decommission plan documented with rollback procedures\n\n## References\n\n- NIST SP 800-207: Zero Trust Architecture\n- CISA Zero Trust Maturity Model v2.0 - Network Pillar\n- Zscaler Private Access Architecture Guide\n- CSA Software-Defined Perimeter and Zero Trust Specification v2.0\n","# Implementing Zero Trust Network Access with Zscaler\n\n## Prerequisites\n\n- Understanding of zero trust principles (NIST SP 800-207)\n- Familiarity with identity providers (Okta, Azure AD, Ping Identity)\n- Knowledge of network security fundamentals\n- Access to Zscaler Private Access (ZPA) tenant\n\n## Overview\n\nZero Trust Network Access (ZTNA) replaces traditional VPN architectures by enforcing identity-based, context-aware access to private applications without placing users on the corporate network. Zscaler Private Access (ZPA) is a leading ZTNA solution that brokers secure connections between authenticated users and internal applications through the Zscaler Zero Trust Exchange cloud platform.\n\nThis skill covers end-to-end deployment of ZPA including connector setup, application segmentation, policy configuration, and integration with identity providers for continuous verification.\n\n## When to Use\n\n- When deploying or configuring implementing zero trust network access with zscaler 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- Familiarity with zero trust architecture concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Architecture\n\n### Zscaler Private Access Components\n\n1. **Client Connector**: Lightweight agent on user endpoints that establishes outbound TLS tunnels to the nearest ZPA Service Edge\n2. **ZPA Service Edge**: Cloud-hosted broker (or Private Service Edge on-premises) that stitches user-to-app connections after policy evaluation\n3. **App Connector**: Lightweight VM deployed in the application environment that creates outbound tunnels to the Service Edge\n4. **ZPA Admin Portal**: Centralized management console for defining applications, segments, and access policies\n\n### Connection Flow\n\n```\nUser Device (Client Connector)\n    |\n    v [Outbound TLS tunnel]\nZPA Service Edge (Policy Evaluation + IdP Auth)\n    |\n    v [Outbound TLS tunnel]\nApp Connector --> Internal Application\n```\n\nKey principle: No inbound connections are required. Both the Client Connector and App Connector initiate outbound-only connections, eliminating the attack surface of traditional VPNs.\n\n## Key Concepts\n\n### Application Segments\nDefine specific applications or groups of applications by IP address, FQDN, port, and protocol. Segments enable granular microsegmentation rather than broad network access.\n\n### Access Policies\nPolicies combine user identity, group membership, device posture, and contextual signals (location, time) to grant or deny access to application segments.\n\n### Server Groups\nLogical groupings of App Connectors that serve specific application segments, enabling high availability and geographic distribution.\n\n### Browser Access\nZPA supports clientless browser-based access for web applications, enabling ZTNA for unmanaged devices and third-party users without requiring the Client Connector.\n\n## Workflow\n\n### Phase 1: Foundation Setup\n\n1. **Configure Identity Provider Integration**\n   - Navigate to Administration > IdP Configuration in ZPA Admin Portal\n   - Add SAML 2.0 or OIDC integration with your IdP (Azure AD, Okta, Ping)\n   - Configure SCIM provisioning for automatic user\u002Fgroup synchronization\n   - Test SSO authentication flow\n\n2. **Deploy App Connectors**\n   - Provision App Connector VMs in each application environment (data center, AWS VPC, Azure VNet)\n   - Download the provisioning key from ZPA Admin Portal\n   - Install and enroll the App Connector using the provisioning key\n   - Verify connector status shows \"Healthy\" in the admin portal\n   - Deploy at least two connectors per environment for high availability\n\n3. **Create Server Groups**\n   - Group App Connectors by geographic location or application tier\n   - Configure health check intervals and failover behavior\n\n### Phase 2: Application Segmentation\n\n4. **Define Application Segments**\n   - Create segments for each application or logical group\n   - Specify domains\u002FIPs, ports, and protocols\n   - Associate segments with appropriate server groups\n   - Enable or disable browser access as needed\n\n5. **Create Segment Groups**\n   - Organize application segments into logical groups (e.g., HR apps, Finance apps)\n   - Use segment groups to simplify policy management\n\n### Phase 3: Policy Configuration\n\n6. **Configure Access Policies**\n   - Define rules matching user groups to application segments\n   - Apply conditions: device posture, client type, SAML attributes\n   - Order rules by priority (most restrictive first)\n   - Create deny rules for blocked access scenarios\n\n7. **Enable Device Posture Checks**\n   - Configure posture profiles requiring OS patch level, disk encryption, antivirus status\n   - Integrate with endpoint management (CrowdStrike, Microsoft Intune, Carbon Black)\n   - Associate posture profiles with access policies\n\n### Phase 4: Client Deployment\n\n8. **Deploy Client Connector**\n   - Package the Zscaler Client Connector with enrollment token\n   - Deploy via MDM (Intune, Jamf, SCCM) or manual installation\n   - Configure forwarding profile to route private app traffic through ZPA\n   - Test user authentication and application access\n\n### Phase 5: Monitoring and Optimization\n\n9. **Enable Logging and Monitoring**\n   - Configure log streaming to SIEM (Splunk, Sentinel, QRadar)\n   - Set up alerts for policy violations, connector health, and authentication failures\n   - Review ZPA Insights dashboard for usage analytics\n\n10. **Iterative Refinement**\n    - Analyze access logs to identify shadow IT and unauthorized access attempts\n    - Refine application segments based on actual traffic patterns\n    - Expand coverage from pilot applications to full enterprise deployment\n\n## Validation Checklist\n\n- [ ] Identity provider integration tested with SSO and SCIM sync\n- [ ] App Connectors deployed and showing healthy status in all environments\n- [ ] Application segments defined with correct IPs\u002FFQDNs, ports, protocols\n- [ ] Access policies enforce least-privilege per user group\n- [ ] Device posture checks block non-compliant endpoints\n- [ ] Client Connector deployed to all managed endpoints\n- [ ] Log streaming to SIEM confirmed with test events\n- [ ] Failover tested by disabling one App Connector per server group\n- [ ] Browser Access configured for web apps requiring third-party access\n- [ ] VPN decommission plan documented with rollback procedures\n\n## References\n\n- NIST SP 800-207: Zero Trust Architecture\n- CISA Zero Trust Maturity Model v2.0 - Network Pillar\n- Zscaler Private Access Architecture Guide\n- CSA Software-Defined Perimeter and Zero Trust Specification v2.0\n",{"name":5,"domain":24,"description":7},"main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Fcloud-zerotrust-zscaler-zia","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill cloud-zerotrust-zscaler-zia",{"tool":46,"command":47},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill cloud-zerotrust-zscaler-zia",{"tool":49,"command":50},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill cloud-zerotrust-zscaler-zia","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud-zerotrust-zscaler-zia\u002FSKILL.md",true,[54],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"index.json","REFERENCE","参考文档",545,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud-zerotrust-zscaler-zia\u002Findex.json",[61,86,109,130,152,168],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":28},"01M71HAPZ01KQ30RKTB0FFSQ05","services-wmi-persistence-detect","Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fpersistence\u002Fdetect\u002FSKILL.md",[],[68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,24,85],"services","detect","services wmi persistence detect","wmi","persistence","de","cm","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","process-forensics",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":28},"01M71HAK6JTTTS229T17WJMMCG","services-wmi-exec-exploit","Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fexec\u002Fexploit\u002FSKILL.md",[],[93,68,94,71,95,96,97,24,98,99,100,101,102,103,73,104,105,106,107,108],"exploit","services wmi exec exploit","exec","remote","traffic","Bash","analysis","team","across","crackmapexec","native","command","lateral movement","read","lateral-movement","Impacket",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":28},"01M71HAG6MHKNQV8KDZKMT4886","registry-artifact-extract","Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fregistry\u002Fartifact\u002Fextract\u002FSKILL.md",[],[116,117,118,119,120,121,24,98,122,99,123,124,73,106,26,125,126,127,128,129],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","activity","digital-forensics","windows-registry","regripper","sonnet",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":28},"01M71HACR4A8XTWTTSXK4124AA","processes-token-impersonate-detect","Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Ftoken\u002Fimpersonate\u002Fdetect\u002FSKILL.md",[],[69,137,138,139,140,141,142,74,143,24,85,144,145,146,147,148,149,150,151,73],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":28},"01M71HAABSB4Z6QFSXEG00R4RK","processes-thread-injection-detect","Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fthread\u002Finjection\u002Fdetect\u002FSKILL.md",[],[159,160,69,161,139,141,162,74,163,143,24,85,99,164,165,166,167,151,73,75],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":28},"01M71HA7H311V5G14WMX58HQSS","processes-hollow-technique-detect","Detect process hollowing (RunPE) by identifying processes with mismatched image paths between PEB and VAD tree, or unmapped PE headers in memory.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fhollow\u002Ftechnique\u002Fdetect\u002FSKILL.md",[],[175,69,139,176,162,74,177,178,24,85,179,180,181,182,183,184,73,75,185,186],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]