AgentStack
SKILL verified MIT Self-run

Oci Zpr Visibility

skill-adibirzu-oci-skills-oci-zpr-visibility · by adibirzu

>-

No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add skill-adibirzu-oci-skills-oci-zpr-visibility

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Oci Zpr Visibility? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

OCI ZPR Visibility

Operate a read-first visibility loop for OCI Zero Trust Packet Routing (ZPR): inventory protected resources and security attributes, correlate VCN Flow Logs, emit sanitized custom records, and validate Log Analytics dashboards. Keep all outputs placeholder-safe.

First move

./scripts/oci_preflight.sh -c "$COMPARTMENT_OCID"
python3 scripts/kb_lookup.py "" zpr

Read [references/zpr-visibility.md](../../references/zpr-visibility.md) before creating collectors, logs, Service Connector Hub connectors, or dashboards.

Common multi-step flows

| Task | Sequence | |---|---| | Build ZPR visibility | preflight → verify ZPR/security-attribute read permissions → enable VCN Flow Logs for selected resources → create custom log + LA source/dashboard → run collector → validate Logging and LA rows | | Triage a rejected flow | collect current ZPR inventory → fetch VCN Flow Logs → correlate flow tuple to protected resources/security attributes → classify as expected reject vs suspected_misconfiguration | | Triage an accepted risky flow | correlate flow to ZPR policy/security attributes → classify unexpected_accepted as review queue → verify policy intent before any mutation | | Import dashboard content | validate parser/source/fields → parse every dashboard query → dry-run dashboard import → apply idempotently → confirm dashboard HIT status |

Safety notes

  • ZPR visibility is mostly read/observe. Enabling ZPR enforcement or changing

policies can break live connectivity; require explicit confirmation.

  • Treat unexpected_accepted as a review queue, not proof of bypass.
  • Treat suspected_misconfiguration as a connectivity triage queue, not proof

that ZPR itself is wrong.

  • Never commit security attribute names from a real tenant if they identify

topology or business domains. Use placeholders.

Expected output

Finding:      
Evidence:     
Action:       
Verification: 
KB:           

Official documentation

OCI Documentation · Logging · Log Analytics

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.