Receber por email
← Voltar para o catálogo

Liongard Inspections

Use this skill when working with Liongard inspectors, launchpoints, inspection scheduling, or triggering inspections on demand. Covers inspector templates, launchpoint configuration, cron schedules, running inspections, and troubleshooting failed runs.

31estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add wyre-technology/msp-claude-plugins

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/liongard-inspections/svg)](https://www.skillteca.com.br/skills/liongard-inspections)
#ai

Skills relacionadas

Ver todas de Documentos →

Alerta por categoria

Receba novas skills de Documentos toda segunda

1 email curto, só com as skills novas de Documentos. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Liongard Inspections & Launchpoints

Overview

Inspections are the core mechanism by which Liongard captures IT documentation. The inspection system consists of three key components:

  • Inspectors - Templates defining what to inspect (e.g., Active Directory, Office 365, Meraki)
  • Launchpoints - Configured instances tying an inspector to an environment, agent, credentials, and schedule
  • Inspections - Individual execution runs that produce system data and potentially trigger detections

The relationship flows: Inspector (template) -> Launchpoint (configuration) -> Inspection (execution) -> System (discovered data)

Inspectors

What Are Inspectors?

Inspectors are pre-built templates provided by Liongard that define what technology platform to inspect and what data to collect. Liongard provides hundreds of built-in inspectors covering:

| Category | Examples | |----------|---------| | Identity & Access | Active Directory, Azure AD, Duo Security, Okta | | Email & Collaboration | Microsoft 365, Google Workspace, Exchange | | Networking | Cisco Meraki, Fortinet, SonicWall, Ubiquiti | | Virtualization | VMware vSphere, Hyper-V, Nutanix | | Backup & DR | Datto, Veeam, Acronis, StorageCraft | | Security | SentinelOne, Sophos, Bitdefender, Huntress | | Cloud | AWS, Azure, GCP | | Infrastructure | Windows Server, Linux, DNS, DHCP, Certificates |

List Inspectors

GET /api/v1/inspectors?page=1&pageSize=100
X-ROAR-API-KEY: {api_key}

Response:

{
  "Data": [
    {
      "ID": 100,
      "Name": "Active Directory",
      "Description": "Inspects Active Directory domain controllers, users, groups, GPOs",
      "Category": "Identity & Access",
      "Version": "3.2.1",
      "RequiresAgent": true,
      "CredentialType": "Domain Admin"
    },
    {
      "ID": 101,
      "Name": "Microsoft 365",
      "Description": "Inspects M365 tenant configuration, users, licenses, security",
      "Category": "Email & Collaboration",
      "Version": "4.1.0",
      "RequiresAgent": false,
      "CredentialType": "App Registration"
    }
  ],
  "TotalRows": 250,
  "HasMoreRows": true,
  "CurrentPage": 1,
  "TotalPages": 3,
  "PageSize": 100
}

Get Inspector by ID

GET /api/v1/inspectors/{inspectorId}
X-ROAR-API-KEY: {api_key}

Response:

{
  "ID": 100,
  "Name": "Active Directory",
  "Description": "Inspects Active Directory domain controllers, users, groups, GPOs",
  "Category": "Identity & Access",
  "Version": "3.2.1",
  "RequiresAgent": true,
  "CredentialType": "Domain Admin",
  "DataPoints": [
    "Users",
    "Groups",
    "Group Policy Objects",
    "Domain Controllers",
    "Organizational Units",
    "DNS Zones",
    "DHCP Scopes",
    "Certificate Authorities"
  ]
}

Inspector Fields

| Field | Type | Description | |-------|------|-------------| | ID | int | Unique inspector identifier | | Name | string | Inspector display name | | Description | string | What the inspector checks | | Category | string | Technology category | | Version | string | Inspector version | | RequiresAgent | boolean | Whether a local agent is needed | | CredentialType | string | Type of credentials required | | DataPoints | array | List of data points collected |

Launchpoints

What Are Launchpoints?

Launchpoints are the configured instances that bring together all components needed to run an inspection:

| Component | Purpose | |-----------|---------| | Inspector | Which template to use | | Environment | Which customer this is for | | Agent | Which agent runs the inspection | | Credentials | How to authenticate to the target | | Schedule | When to run inspections | | Configuration | Inspector-specific settings |

Launchpoint Fields

| Field | Type | Required | Description | |-------|------|----------|-------------| | ID | int | System | Unique launchpoint identifier | | InspectorID | int | Yes | Associated inspector template | | EnvironmentID | int | Yes | Target environment | | AgentID | int | Conditional | Agent to use (if inspector requires) | | Name | string | Yes | Launchpoint display name | | Status | string | No | Active, Inactive, Error | | Schedule | string | No | Cron expression for scheduling | | LastInspection | datetime | System | Last successful inspection | | NextInspection | datetime | System | Next scheduled inspection | | CreatedOn | datetime | System | Creation timestamp | | UpdatedOn | datetime | System | Last update timestamp |

List Launchpoints

GET /api/v1/launchpoints?page=1&pageSize=100
X-ROAR-API-KEY: {api_key}

Response:

{
  "Data": [
    {
      "ID": 5001,
      "InspectorID": 100,
      "EnvironmentID": 1234,
      "AgentID": 501,
      "Name": "Acme Corp - Active Directory",
      "Status": "Active",
      "Schedule": "0 2 * * *",
      "LastInspection": "2024-02-15T02:00:00Z",
      "NextInspection": "2024-02-16T02:00:00Z",
      "CreatedOn": "2023-06-01T10:00:00Z",
      "UpdatedOn": "2024-02-15T02:15:00Z"
    }
  ],
  "TotalRows": 500,
  "HasMoreRows": true,
  "CurrentPage": 1,
  "TotalPages": 5,
  "PageSize": 100
}

Filter Launchpoints by Environment

GET /api/v1/launchpoints?environmentId={environmentId}&page=1&pageSize=100
X-ROAR-API-KEY: {api_key}

Get Launchpoint by ID

GET /api/v1/launchpoints/{launchpointId}
X-ROAR-API-KEY: {api_key}

Create Launchpoint

POST /api/v1/launchpoints
X-ROAR-API-KEY: {api_key}
Content-Type: application/json
{
  "InspectorID": 100,
  "EnvironmentID": 1234,
  "AgentID": 501,
  "Name": "Acme Corp - Active Directory",
  "Schedule": "0 2 * * *",
  "Configuration": {
    "DomainController": "dc01.acme.local",
    "Username": "admin@acme.local",
    "Password": "encrypted-credential-reference"
  }
}

Response:

{
  "ID": 5002,
  "InspectorID": 100,
  "EnvironmentID": 1234,
  "AgentID": 501,
  "Name": "Acme Corp - Active Directory",
  "Status": "Active",
  "Schedule": "0 2 * * *",
  "CreatedOn": "2024-02-15T09:00:00Z"
}

Update Launchpoint

PUT /api/v1/launchpoints/{launchpointId}
X-ROAR-API-KEY: {api_key}
Content-Type: application/json
{
  "Schedule": "0 3 * * *",
  "Name": "Acme Corp - Active Directory (Updated)"
}

Delete Launchpoint

DELETE /api/v1/launchpoints/{launchpointId}
X-ROAR-API-KEY: {api_key}

Warning: Deleting a launchpoint removes all associated systems and historical inspection data.

Scheduling

Cron Expression Format

Launchpoints use standard cron expressions for scheduling:

┌───────── minute (0-59)
│ ┌─────── hour (0-23)
│ │ ┌───── day of month (1-31)
│ │ │ ┌─── month (1-12)
│ │ │ │ ┌─ day of week (0-6, Sun=0)
│ │ │ │ │
* * * * *

Common Schedules

| Cron Expression | Description | |-----------------|-------------| | 0 2 | Daily at 2:00 AM | | 0 /6 | Every 6 hours | | 0 0 0 | Weekly on Sunday at midnight | | 0 8 1 | Monthly on the 1st at 8:00 AM | | /30 | Every 30 minutes | | 0 2 1-5 | Weekdays at 2:00 AM |

Scheduling Best Practices

  1. Stagger inspection times - Avoid running all launchpoints at the same time
  2. Use off-peak hours - Schedule during client off-hours (e.g., 2:00 AM)
  3. Match frequency to change rate - Daily for AD/O365, weekly for static infrastructure
  4. Consider agent load - Don't overload agents with concurrent inspections
  5. Account for time zones - Schedule based on the client's local time

Running Inspections On Demand

Trigger Immediate Inspection

POST /api/v1/launchpoints/{launchpointId}/run
X-ROAR-API-KEY: {api_key}

Response:

{
  "InspectionID": 99001,
  "LaunchpointID": 5001,
  "Status": "Queued",
  "QueuedAt": "2024-02-15T14:30:00Z"
}

Inspection Status Values

| Status | Description | |--

Compartilhar X LinkedIn