slug: ninjaone
provider: NinjaOne
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 6
edges:
- tag: Ticketing
  spec_file: ninjaone-ticketing-api-openapi.yml
  capability_id: BC-600.30
  capability_id_l1: BC-600
  capability_name: IT Service Management
  confidence: 0.85
  evidence: POST /v2/ticketing/ticket create Create ticket; GET /v2/ticketing/statuses getAllStatuses
    Get list of ticket status; TicketFormPublicApiDTO
  reason: Full IT service-desk ticket lifecycle (create, comment, update, log entries, statuses, boards)
    on an IT operations platform, i.e. ITSM incident/request handling rather than generic customer service.
- tag: Vulnerability Management
  spec_file: ninjaone-vulnerability-management-api-openapi.yml
  capability_id: BC-620.40
  capability_id_l1: BC-620
  capability_name: Vulnerability Management
  confidence: 0.85
  evidence: GET /v2/vulnerability/scan-groups fetchAllScanGroups Fetch all Scan Groups
  reason: Vulnerability scan group retrieval and CSV upload under /v2/vulnerability — vulnerability scanning
    and remediation tracking, matching Vulnerability Management directly.
- tag: Knowledge Base Articles
  spec_file: ninjaone-knowledge-base-articles-api-openapi.yml
  capability_id: BC-830
  capability_id_l1: BC-830
  capability_name: Knowledge Management
  confidence: 0.8
  evidence: POST /v2/knowledgebase/articles createKnowledgeBaseArticles; GET /v2/knowledgebase/global/articles
    getGlobalKnowledgeBaseArticles Lists global knowledge base articles
  reason: Full lifecycle of knowledge base articles and folders (create, update, archive, delete, download,
    attachments) — organisational knowledge capture, curation and sharing. L1 Knowledge Management; article
    vs folder/curation split is ambiguous so no L2.
- tag: Devices
  spec_file: ninjaone-devices-api-openapi.yml
  capability_id: BC-600.40
  capability_id_l1: BC-600
  capability_name: IT Operations Management
  confidence: 0.75
  evidence: GET /v2/device/{id}/alerts getDeviceAlerts Device alerts (triggered conditions); GET /v2/device/{id}/os-patch-installs
    OS Patch installation report for device
  reason: Operations expose endpoint device inventory details (disks, processors, network interfaces),
    running jobs, triggered alerts and OS/software patch state — day-to-day IT endpoint operations, monitoring
    and patching. Maps to IT Operations Management; some overlap with infrastructure/asset management
    keeps confidence moderate.
- tag: Backup
  spec_file: ninjaone-backup-api-openapi.yml
  capability_id: BC-160.20
  capability_id_l1: BC-160
  capability_name: Disaster Recovery Management
  confidence: 0.7
  evidence: GET /v2/backup/jobs Backup jobs; POST /v2/backup/integrity-check-jobs Create an integrity
    check job
  reason: Endpoint backup job monitoring and integrity verification — IT backup/recovery operations. Maps
    to Disaster Recovery Management (IT backup), though it could equally sit under IT Operations Management.
- tag: Unmanaged Devices
  spec_file: ninjaone-unmanaged-devices-api-openapi.yml
  capability_id: BC-600
  capability_id_l1: BC-600
  capability_name: Information Technology Management
  confidence: 0.7
  evidence: POST /v2/itam/unmanaged-device createUnmanagedDevicePublicApi Create an Unmanaged Device
  reason: The /itam/ path and device CRUD indicate IT asset management of non-agent devices. Clearly IT
    management, but no candidate L2 corresponds cleanly to IT asset inventory, so only the L1 is asserted.