AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Cipp Alerts

skill-wyre-technology-msp-claude-plugins-alerts · by wyre-technology

Use this skill when working with CIPP alerts and audit logs — reviewing the queued alert backlog across tenants, investigating sign-in or admin activity in audit logs, correlating alerts with tenants. Read-only triage surface for the CIPP alerting subsystem.

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

Install

$ agentstack add skill-wyre-technology-msp-claude-plugins-alerts

✓ 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-wyre-technology-msp-claude-plugins-alerts)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Cipp Alerts? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

CIPP Alerts & Audit Logs

CIPP raises alerts based on standards violations, anomaly detection, and configured thresholds. The two tools in this skill let you triage the alert queue and pull underlying audit log evidence.

Tools

cipp_list_alert_queue

cipp_list_alert_queue()

Returns queued alerts across all tenants — alert type, tenant, severity, raised time, and current status. This is your daily triage list.

cipp_list_audit_logs

cipp_list_audit_logs(tenantFilter='contoso.onmicrosoft.com',
                     startDate?, endDate?,
                     userId?, operation?)

Tenant-scoped audit log entries from the M365 unified audit log. Filter by date range, user, or operation to narrow investigation scope. Use to investigate suspicious sign-ins, admin role changes, mailbox access, app consent grants, and policy modifications.

Workflow patterns

Daily alert triage

  1. cipp_list_alert_queue — pull the full queue
  2. Group by tenant + alertType to spot patterns (one tenant generating most alerts often signals a broken standard or runaway script)
  3. Triage in severity order: critical → high → medium → low
  4. For each alert: drill into the related tenant's audit logs with cipp_list_audit_logs filtered to the alert window

Correlate alert → audit evidence

alerts = cipp_list_alert_queue()
critical = [a for a in alerts if a['severity'] == 'critical']
for a in critical:
    logs = cipp_list_audit_logs(
        tenantFilter=a['tenantId'],
        startDate=a['raisedAt'] - 30 minutes,
        endDate=a['raisedAt'] + 5 minutes,
    )

The 30-minute lookback usually captures the precipitating event (sign-in, admin change, app consent) that caused the alert.

Common audit operations to filter on

| operation value | What it surfaces | |-------------------|------------------| | UserLoggedIn | Sign-in events | | Add member to role | Role escalation | | Consent to application | New app permissions granted | | New-InboxRule | Mailbox rule creation (BEC indicator) | | Set-Mailbox | Mailbox config changes | | Add policy | Conditional access policy created | | Update conditional access policy | CA policy modified |

Investigating a suspected compromise

When cipp_bec_check flags a user, supplement it with audit log queries:

  1. Pull all UserLoggedIn operations for the user over the last 7 days — look for unusual countries, IPs, or bursts of failed → success patterns
  2. Pull all New-InboxRule and Set-Mailbox operations — hidden forwarding/auto-delete rules
  3. Pull all Consent to application operations — illicit consent grants are common BEC vectors

Caveats

  • The unified audit log has a lag (typically minutes, sometimes hours) — recent events may not appear immediately.
  • Audit retention varies by license: 90 days for E3, 1 year for E5, longer with audit log retention add-ons. Plan investigations around what the tenant's licensing actually allows.
  • cipp_list_alert_queue returns active queue items — historic resolved alerts require the CIPP UI.

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.