zins-analyze-web-traffic
Analyze web traffic patterns using Zscaler Analytics (Z-Insights). Examines traffic distribution by location, protocol breakdown (HTTP vs HTTPS), threat categories, DLP violations, and volume trends over time. Use when an administrator asks: 'Show me web traffic by location', 'What protocols are in use?', 'Are there any DLP violations?', 'What does our traffic look like?', or 'Show traffic trends.'
What this skill does
# Z-Insights: Analyze Web Traffic Patterns
## Keywords
web traffic, traffic analytics, traffic by location, protocol distribution, HTTP HTTPS, DLP violations, traffic volume, traffic trends, bandwidth, capacity planning, web analytics, traffic report, data loss prevention
## Overview
Analyze web traffic across your organization using the Zscaler Analytics (Z-Insights) GraphQL API. This skill retrieves traffic data by location, protocol distribution, threat categories, and overall volume. It supports DLP filtering, trend analysis, and allows measurement in transactions or bytes.
**Use this skill when:** An administrator or security analyst needs to understand web traffic patterns, plan capacity, monitor protocol adoption (e.g., HTTPS migration), investigate DLP policy violations, or generate traffic reports for specific time periods.
**Important constraints:**
- Z-Insights only supports **historical data** with a 24-48 hour processing delay
- Time ranges must be exactly **7 or 14 days** (the API enforces this)
- Use `start_days_ago` / `end_days_ago` (recommended) or epoch milliseconds
- Set `end_days_ago` to at least **2** to ensure data availability
---
## Workflow
Follow this 5-step process to analyze web traffic.
### Step 1: Understand the Analysis Request
Gather from the analyst:
- What aspect of traffic? (volume, locations, protocols, threats, DLP)
- What time period? (past week = 7 days, past two weeks = 14 days)
- Measurement unit? (TRANSACTIONS for request counts, BYTES for bandwidth)
- Any specific filters? (DLP engine, allow/block actions)
- Need trend data? (daily or hourly granularity)
---
### Step 2: Analyze Traffic by Location
**Get web traffic distribution across locations:**
```text
zins_get_web_traffic_by_location(
start_days_ago=9,
end_days_ago=2,
traffic_unit="TRANSACTIONS",
limit=20
)
```text
This identifies which offices, branches, or regions generate the most web traffic. Look for:
- Top traffic-generating locations (potential bandwidth bottlenecks)
- Unusual traffic spikes at specific locations
- Remote vs office traffic distribution
**With trend data for capacity planning:**
```text
zins_get_web_traffic_by_location(
start_days_ago=9,
end_days_ago=2,
traffic_unit="BYTES",
include_trend=True,
trend_interval="DAY",
limit=10
)
```text
---
### Step 3: Analyze Protocol Distribution
**Get protocol breakdown:**
```text
zins_get_web_protocols(
start_days_ago=9,
end_days_ago=2,
traffic_unit="TRANSACTIONS",
limit=20
)
```text
Evaluate:
- **HTTPS adoption**: What percentage of traffic is encrypted?
- **HTTP traffic**: Remaining unencrypted traffic may indicate legacy applications or misconfigured services
- **Other protocols**: SSL, FTP over HTTP, WebSocket, etc.
- **Anomalies**: Unexpected protocol usage may indicate malware or policy bypass
---
### Step 4: Analyze Overall Traffic Volume and DLP
**Get total traffic volume (no grouping):**
```text
zins_get_web_traffic_no_grouping(
start_days_ago=9,
end_days_ago=2,
traffic_unit="TRANSACTIONS"
)
```text
**Filter by DLP violations:**
```text
zins_get_web_traffic_no_grouping(
start_days_ago=9,
end_days_ago=2,
dlp_engine_filter="PCI",
traffic_unit="TRANSACTIONS"
)
```text
Available DLP engine filters:
- `ANY` -- any DLP engine triggered
- `NONE` -- no DLP engine triggered
- `HIPAA` -- healthcare data violations
- `PCI` -- payment card data violations
- `GLBA` -- financial data violations
- `CYBER_BULLY_ENG` -- cyberbullying content
- `OFFENSIVE_LANGUAGE` -- offensive content
- `EXTERNAL` -- external DLP engine
**Filter by action:**
```text
zins_get_web_traffic_no_grouping(
start_days_ago=9,
end_days_ago=2,
action_filter="BLOCK",
traffic_unit="TRANSACTIONS"
)
```text
**Get volume trends over time:**
```text
zins_get_web_traffic_no_grouping(
start_days_ago=9,
end_days_ago=2,
include_trend=True,
trend_interval="DAY",
traffic_unit="BYTES"
)
```text
---
### Step 5: Check Threat Activity in Web Traffic
**Get threat super categories:**
```text
zins_get_threat_super_categories(
start_days_ago=9,
end_days_ago=2,
traffic_unit="TRANSACTIONS",
limit=20
)
```text
This shows high-level threat categories (malware, phishing, spyware, C2, etc.) detected in web traffic.
**Get detailed threat classifications:**
```text
zins_get_threat_class(
start_days_ago=9,
end_days_ago=2,
traffic_unit="TRANSACTIONS",
limit=20
)
```text
This breaks threats into specific types (virus, trojan, ransomware, exploit kit, cryptominer, etc.).
---
### Present Analysis
```text
Web Traffic Analysis Report
=============================
Date: <current_date>
Period: <start_date> to <end_date> (7-day / 14-day interval)
## Traffic Summary
- **Total Transactions:** X,XXX,XXX
- **Total Data Volume:** XX.X GB
- **Blocked Transactions:** X,XXX (X.X% of total)
- **DLP Violations:** X,XXX
---
## Traffic by Location (Top 10)
| Rank | Location | Transactions | % of Total | Trend |
|------|---------------------|-------------|-----------|------------|
| 1 | New York HQ | 450,000 | 32% | Stable |
| 2 | San Francisco | 280,000 | 20% | ↑ 15% |
| 3 | London | 195,000 | 14% | Stable |
| ... | ... | ... | ... | ... |
---
## Protocol Distribution
| Protocol | Transactions | % of Total | Assessment |
|----------|-------------|-----------|-------------------|
| HTTPS | 1,200,000 | 87% | Good adoption |
| HTTP | 140,000 | 10% | Review needed |
| SSL | 35,000 | 2.5% | Normal |
| Other | 7,000 | 0.5% | Monitor |
HTTPS adoption at 87% -- target is 95%+. HTTP traffic sources
should be investigated for possible migration to HTTPS.
---
## Threat Detections
| Category | Count | Trend vs Previous |
|-----------------|--------|-------------------|
| Malware | 2,340 | ↑ 12% |
| Phishing | 1,890 | ↓ 5% |
| Spyware | 890 | Stable |
| Adware | 567 | ↓ 20% |
---
## DLP Summary
| DLP Engine | Violations | Action |
|-----------|-----------|---------|
| PCI | 145 | Blocked |
| HIPAA | 89 | Blocked |
| GLBA | 23 | Blocked |
---
## Recommendations
1. Investigate HTTP traffic sources for HTTPS migration
2. Review the 12% increase in malware detections
3. <location> shows unusual traffic spike -- verify with local IT
4. PCI violations trending up -- review DLP policy exceptions
```text
---
## Edge Cases
### No Data Returned
```text
Z-Insights returned no data for the specified time range.
Possible causes:
- Z-Insights/Business Insights may not be licensed for this tenant
- The time range may be outside the supported window
- Data has a 24-48 hour processing delay
Action: Verify Z-Insights licensing and try a time range ending
at least 2 days ago.
```text
### Time Range Errors
```text
The Z-Insights API requires time intervals of exactly 7 or 14 days.
Use these parameter combinations:
- 7-day: start_days_ago=9, end_days_ago=2
- 14-day: start_days_ago=16, end_days_ago=2
The tool auto-adjusts intervals when using days_ago parameters.
```text
---
## Quick Reference
**Primary workflow:** Scope → Locations → Protocols → Volume/DLP → Threats → Report
**Traffic tools:**
- `zins_get_web_traffic_by_location()` -- traffic distribution by location
- `zins_get_web_traffic_no_grouping()` -- overall traffic volume with DLP and action filters
- `zins_get_web_protocols()` -- protocol distribution (HTTP, HTTPS, SSL, etc.)
**Threat tools:**
- `zins_get_threat_super_categories()` -- high-level threat categories
- `zins_get_threat_class()` -- detailed threat classifications
**Common parameters:**
- `startRelated in Security
mac-ops
IncludedComprehensive macOS workstation operations — diagnose kernel panics, identify failing drives, audit launchd startup items, decode wake reasons, triage TCC permission denials, manage APFS snapshots, recover from no-boot. Use for: Mac is slow, slow bootup, won't boot, kernel panic, kernel_task hot, mds_stores CPU, photoanalysisd, cloudd, login loop, gray screen, sleep wake failure, drive failing, IO errors, APFS snapshots eating space, Time Machine local snapshots, Spotlight indexing, launchd, LaunchAgent, LaunchDaemon, login items, TCC permissions, Full Disk Access, Screen Recording denied, Gatekeeper, quarantine, com.apple.quarantine, app is damaged, helper tool, /Library/PrivilegedHelperTools, pmset, wake reasons, dark wake, sysdiagnose, panic.ips, DiagnosticReports, configuration profile, MDM profile, remote diagnostics over SSH.
a11y-audit
IncludedRun accessibility audits on web projects combining automated scanning (axe-core, Lighthouse) with WCAG 2.1 AA compliance mapping, manual check guidance, and structured reporting. Output is configurable: markdown report only, markdown plus machine-readable JSON, or markdown plus issue tracker integration. Use this skill whenever the user mentions "accessibility audit", "a11y audit", "WCAG audit", "accessibility check", "compliance scan", or asks to check a web project for accessibility issues. Also trigger when the user wants to verify WCAG conformance or map findings to a specific standard (CAN-ASC-6.2, EN 301 549, ADA/AODA).
erpclaw
IncludedAI-native ERP system with self-extending OS. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting. 413 actions across 14 domains, 43 expansion modules. Constitutional guardrails, adversarial audit, schema migration. Double-entry GL, immutable audit trail, US GAAP.
assess
IncludedAssesses and rates quality 0-10 across multiple dimensions (correctness, maintainability, security, performance, testability, simplicity) with pros/cons analysis. Compares against project conventions and prior decisions from memory. Produces structured evaluation reports with actionable improvement suggestions. Use when evaluating code, designs, architectures, or comparing alternative approaches.
spring-boot-security-jwt
IncludedProvides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based access control using Spring Security 6.x. Use when implementing authentication or authorization in Spring Boot applications.
code-hardcode-audit
IncludedDetect hardcoded values, magic numbers, and leaked secrets. TRIGGERS - hardcode audit, magic numbers, PLR2004, secret scanning.