Source profileQuality 93/100

WYRE-AI/msp-claude-plugins/msp-claude-plugins/cipp/cipp/skills/security/SKILL.md

cipp-security

Read-only access to a tenant's Conditional Access policy graph and named locations through CIPP: policy state semantics, the findings that matter in a CA review, portfolio drift detection, and why CA writes are absent from the MCP surface.

Source repository stars
42
Declared platforms
0
Static risk flags
0
Last source update
2026-08-28
Source checked
2026-08-28

Decision brief

What it does: where it fits

Read-only access to a tenant's Conditional Access policy graph and named-location list. Use as input to security posture reviews and to detect tenants drifting from MSP baseline policies. CIPP doesn't expose CA write operations through MCP — apply policy changes via CIPP standar…

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/WYRE-AI/msp-claude-plugins --skill "msp-claude-plugins/cipp/cipp/skills/security"
    Safe inspection promptEditorial

    Inspect the Agent Skill "cipp-security" from https://github.com/WYRE-AI/msp-claude-plugins/blob/5005f73ba2f52cd299f58aa6bb79f4e70ae87103/msp-claude-plugins/cipp/cipp/skills/security/SKILL.md at commit 5005f73ba2f52cd299f58aa6bb79f4e70ae87103. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      What to look for in a CA review

      Review the “What to look for in a CA review” section in the pinned source before continuing.

      Review and apply the “What to look for in a CA review” source section.
    2. 02

      Workflow patterns

      If mfaforallapps is false, the tenant lacks the baseline "MFA for everything" policy that every MSP should ship as a standard.

      If mfaforallapps is false, the tenant lacks the baseline "MFA for everything" policy that every MSP should ship as a standard.Run cipplistconditionalaccesspolicies per tenant and compare the policy fingerprint (display names + state + grant controls) against the MSP's golden baseline. Flag tenants where any baseline policy is missing or disabl…
    3. 03

      Anti-triggers

      Creating, editing, or deploying a CA policy — there is no CA

      Creating, editing, or deploying a CA policy — there is no CAWho has actually registered MFA — CA tells you what is required,Defender, secure score, or threat policies for one tenant you hold
    4. 04

      Tools

      Returns every CA policy with displayName, state (enabled / disabled / enabledForReportingButNotEnforced), conditions (users, apps, locations, platforms, sign-in risk), and grantControls (MFA, compliant device, terms of use, etc).

      Returns every CA policy with displayName, state (enabled / disabled / enabledForReportingButNotEnforced), conditions (users, apps, locations, platforms, sign-in risk), and grantControls (MFA, compliant device, terms of…Returns named locations: IP ranges (trusted/untrusted) and country-based locations. These are the building blocks CA policies reference for location-based controls.

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score93/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars42SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    WYRE-AI/msp-claude-plugins
    Skill path
    msp-claude-plugins/cipp/cipp/skills/security/SKILL.md
    Commit
    5005f73ba2f52cd299f58aa6bb79f4e70ae87103
    License
    Apache-2.0
    Collected
    2026-08-28
    Default branch
    main
    View the original SKILL.md

    CIPP Security — Conditional Access & Named Locations

    Read-only access to a tenant's Conditional Access policy graph and named-location list. Use as input to security posture reviews and to detect tenants drifting from MSP baseline policies. CIPP doesn't expose CA write operations through MCP — apply policy changes via CIPP standards or the CIPP UI.

    Anti-triggers

    • Creating, editing, or deploying a CA policy — there is no CA write tool here; policy rollout goes through cipp-standards or the CIPP UI.
    • Who has actually registered MFA — CA tells you what is required, not what users have enrolled; cipp_list_mfa_users in cipp-users answers the enrolment question.
    • Defender, secure score, or threat policies for one tenant you hold credentials for — that is the m365 plugin's Microsoft 365 Security; this skill is CSP-delegated and CA-only.
    • Portfolio-wide posture scoring — comparing tenants against a baseline template is cipp-standards or inforcer-compliance-reporting.

    Tools

    cipp_list_conditional_access_policies

    cipp_list_conditional_access_policies(tenantFilter='contoso.onmicrosoft.com')
    

    Returns every CA policy with displayName, state (enabled / disabled / enabledForReportingButNotEnforced), conditions (users, apps, locations, platforms, sign-in risk), and grantControls (MFA, compliant device, terms of use, etc).

    cipp_list_named_locations

    cipp_list_named_locations(tenantFilter='contoso.onmicrosoft.com')
    

    Returns named locations: IP ranges (trusted/untrusted) and country-based locations. These are the building blocks CA policies reference for location-based controls.

    What to look for in a CA review

    FindingWhy it matters
    Zero policies in enabled stateTenant has no CA enforcement at all — a baseline enabledForReportingButNotEnforced doesn't block anything
    MFA not required for "All cloud apps"A baseline policy is missing or scoped too narrowly
    Policies excluding the entire admin roleCommon configuration mistake; admins should require more MFA, not less
    Trusted location includes home/coffee-shop IPsNamed-location bloat creates exception paths for attackers
    legacy authentication not blockedBasic auth bypasses MFA entirely; should be blocked tenant-wide
    Reporting-only policies older than 30 daysShould have been promoted to enabled or removed

    Workflow patterns

    Tenant CA baseline check

    policies = cipp_list_conditional_access_policies(tenantFilter)
    enabled = [p for p in policies if p['state'] == 'enabled']
    mfa_for_all_apps = any(
        p for p in enabled
        if 'mfa' in p.get('grantControls', {}).get('builtInControls', [])
        and 'All' in p.get('conditions', {}).get('applications', {}).get('includeApplications', [])
    )
    

    If mfa_for_all_apps is false, the tenant lacks the baseline "MFA for everything" policy that every MSP should ship as a standard.

    Portfolio drift detection

    Run cipp_list_conditional_access_policies per tenant and compare the policy fingerprint (display names + state + grant controls) against the MSP's golden baseline. Flag tenants where any baseline policy is missing or disabled.

    Caveats

    • CA write operations (create/edit/delete) are not exposed via MCP. Use CIPP standards (cipp_run_standards_check and the standards UI) to deploy policy templates across tenants, or do it manually via the CIPP web UI.
    • Named locations are a trust amplifier — review them as carefully as policies. A misconfigured trusted IP range can quietly exempt entire networks from MFA.
    • enabledForReportingButNotEnforced looks like coverage in dashboards but enforces nothing. Always check state == 'enabled' for actual enforcement.

    Frequently asked questions

    What to verify before installation and use

    What does the cipp-security source document cover?

    Read-only access to a tenant's Conditional Access policy graph and named-location list. Use as input to security posture reviews and to detect tenants drifting from MSP baseline policies. CIPP doesn't expose CA write operations through MCP — apply policy changes via CIPP standar…

    How do I install cipp-security?

    The source record exposes this install command: npx skills add https://github.com/WYRE-AI/msp-claude-plugins --skill "msp-claude-plugins/cipp/cipp/skills/security". Inspect the command and pinned source before running it.

    Alternatives

    Compare before choosing

    Computed 10029,236

    garrytan/gbrain

    bulk-ingestion

    End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.

    Computed 10025,136

    alirezarezvani/claude-skills

    app-store-optimization

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

    Computed 10015,385

    wanshuiyin/Auto-claude-code-research-in-sleep

    citation-audit

    Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.

    Computed 10014,706

    prowler-cloud/prowler

    postgresql-indexing

    PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance