Integration Overview

LanternOps connects to 17+ active integrations across RMM, PSA, security, and business platforms to automatically collect evidence for compliance frameworks.

Why Integrations Matter

The Problem:

• Manual evidence gathering takes 40+ hours per audit
• Data is outdated by the time audits happen
• No way to prove real-time compliance
• Customers can’t see what you’re doing for them

The Solution: Integration data automatically proves your services satisfy compliance controls.

Evidence Collection

What Gets Collected

Every 4-6 hours, LanternOps syncs data from your connected platforms:

Integration Category	Data Collected	Compliance Value
RMM Platforms	Asset inventory, patch status, software inventory, hardware specs	CIS 1.1, 1.2, 7.1, NIST ID.AM-1
Security Tools	EDR coverage, threats detected/blocked, endpoint protection status	CIS 10.1, 13.1, NIST PR.DS-5
Email Security	Phishing blocks, spam filtering, MFA status, DMARC/SPF/DKIM	CIS 16.1, NIST PR.AC-7
PSA Platforms	Tickets, time tracking, service delivery, customer contracts	Evidence of service delivery
Microsoft 365	User accounts, license counts, MFA enrollment, security settings	HIPAA, CIS 5.1, NIST ID.AM-2
DNS Filtering	Malware domains blocked, threat intelligence, network protection	CIS 9.2, NIST DE.CM-1
Backup Systems	Backup completion, restore testing, retention policies	CIS 11.1, NIST PR.IP-4

How Evidence Maps to Compliance

Example: CIS Control 1.1 (Asset Inventory)

Control Requirement:
"Establish and maintain detailed enterprise asset inventory"

LanternOps Evidence:
✅ NinjaRMM: 147 endpoints discovered
✅ Last Sync: 2 hours ago
✅ Asset Details: Make, model, OS, age, warranty
✅ Network Coverage: 100% of network mapped

Status: SATISFIED (95% confidence)

The system automatically understands which integration data satisfies which compliance controls using AI/RAG semantic mapping.

Supported Integrations

Production-Ready (12 Integrations)

These integrations are fully operational with automatic sync:

RMM Platforms

• NinjaOne - Asset management, patch status, software inventory
• Action1 - Endpoint management, patch compliance, security posture
• Syncro - Asset tracking, ticketing, customer management

Security Tools

• Huntress - EDR coverage, threat detection, agent status
• NextDNS - DNS filtering, malware blocking, network security
• PowerDMARC - Email authentication, DMARC/SPF/DKIM compliance

PSA Platforms

• ConnectWise - Ticketing, time tracking, contract management
• Autotask PSA - Service delivery, customer management, billing
• HaloPSA - Ticket tracking, service desk operations

Microsoft & Business

• Microsoft 365 - User accounts, licensing, email security, Teams/Exchange
• Pax8 - Subscription management, licensing, customer products
• Timely - Time tracking, project hours, service delivery proof

Coming Soon (15 Integrations)

In development, available within 60-90 days:

RMM Platforms:

• Datto RMM
• Kaseya VSA
• N-able

Security Platforms:

• Malwarebytes
• SentinelOne
• CrowdStrike

Documentation:

• IT Glue
• Hudu

Collaboration:

• Google Workspace
• Slack
• Microsoft Teams (enhanced)

Business:

• QuickBooks Online
• Xero
• BrightGauge

Auto-Sync Frequency

Each integration syncs automatically on different schedules based on data volatility:

Sync Frequency	Integrations	Reason
Every 1 hour	Microsoft 365	User changes, security events
Every 4 hours	NinjaOne, Huntress, Timely	Asset and agent updates
Every 6 hours	ConnectWise, Autotask, HaloPSA, Syncro, Pax8, NextDNS	Ticketing and contract data
Every 12 hours	PowerDMARC	Email authentication reports

All syncs run automatically in the background. No manual intervention required.

How Auto-Sync Works

The ETL Pipeline

Every integration follows a 4-stage pipeline:

1. Extract

• Connect to integration API
• Pull latest data (incremental when possible)
• Handle rate limits and pagination

2. Transform

• Normalize data to common format
• Map to LanternOps data models
• Auto-match to customers

3. Load

• Store in LanternOps database
• Update compliance mappings
• Calculate business metrics

4. Index

• Add to RAG system for AI analysis
• Update dashboards
• Generate alerts for gaps

Intelligent Customer Matching

LanternOps automatically matches integration data to your customers:

Matching Strategies:

1. Exact Name Match - “Acme Corp” = “Acme Corp”
2. Fuzzy Name Match - “Acme Corporation” = “Acme Corp” (>80% similarity)
3. Domain Match - Email domain matches customer domain
4. Manual Override - You can manually map if auto-match fails

Success Rate: >80% automatic matching across all integrations

Security & Credentials

How Credentials Are Stored

All API keys and secrets are encrypted:

• AES-256 encryption at rest
• Encrypted in database with Fernet encryption
• Never stored in plaintext
• Never logged or exposed in UI

Multi-Tenant Isolation:

• Each MSP’s credentials are completely isolated
• No cross-tenant data access
• Automatic tenant filtering on all queries

Authentication Methods Supported

Integration	Auth Method	Setup Complexity
NinjaOne	OAuth 2.0 or API Key	Medium (OAuth recommended)
Huntress	API Key + Secret	Low
Microsoft 365	OAuth 2.0 (GDAP support)	Medium
ConnectWise	OAuth 2.0	Medium
Autotask	OAuth 2.0	Medium
HaloPSA	API Key	Low
Syncro	API Key	Low
Pax8	API Key	Low
NextDNS	API Key	Low
PowerDMARC	API Key	Low

Monitoring & Health

Integration Health Dashboard

View real-time health of all integrations at /platform/etl/:

Metrics Tracked:

• ✅ Last successful sync timestamp
• ⚠️ Failure rate (target: <5%)
• 📊 Records synced per run
• ⏱️ Average sync duration
• 🔄 Next scheduled sync time

Health Statuses:

• 🟢 Healthy - <5% failure rate, syncing normally
• 🟡 Warning - 5-15% failure rate, some issues
• 🔴 Critical - >15% failure rate, needs attention

Automatic Error Recovery

The ETL system includes intelligent retry logic:

Transient Failures (network issues, rate limits):

• Automatic retry with exponential backoff
• Up to 3 retry attempts
• Dead Letter Queue (DLQ) for failed records

Permanent Failures (auth errors, invalid data):

• Alert sent to MSP admin
• Detailed error message logged
• Requires manual intervention

Recovery Success Rate: 87% (most errors resolve automatically)

Setting Up Integrations

General Setup Process

1. Navigate to Integration Settings

   • Go to your MSP dashboard
   • Click “Integrations” in sidebar
   • Select the integration to configure

2. Enter API Credentials

   • Follow integration-specific guide below
   • Enter API keys/OAuth credentials
   • Test connection

3. Configure Sync Settings

   • Enable auto-sync (recommended)
   • Set sync frequency (or use defaults)
   • Map customers (if manual mapping needed)

4. Verify First Sync

   • Click “Sync Now” to test
   • Check ETL Health Dashboard
   • Verify data appears in Assets/Tickets/etc.

Integration-Specific Guides

Click each integration for detailed setup instructions:

• NinjaOne Setup Guide
• Huntress Setup Guide
• Microsoft 365 Setup Guide
• ConnectWise Setup Guide

Common Issues

”Connection Failed” Error

Cause: Invalid API credentials or network issue

Solution:

1. Verify API key is correct (copy/paste from source)
2. Check API key hasn’t expired
3. Ensure API key has correct permissions
4. Test connection again

”No Data Syncing”

Cause: Sync disabled or customer mapping failed

Solution:

1. Check “Sync Enabled” is turned ON in settings
2. Review customer mapping - verify auto-match worked
3. Check ETL Health Dashboard for errors
4. Try manual “Sync Now” to see specific error

”Partial Data Only”

Cause: API permissions insufficient

Solution:

1. Review API key permissions in source platform
2. Ensure all required scopes are granted:
   • Read access to assets/devices
   • Read access to tickets/time entries
   • Read access to customers/organizations
3. Regenerate API key with full permissions

”Sync Taking Too Long”

Cause: Large data volume on first sync

Solution:

• First sync can take 30-60 minutes (imports all historical data)
• Subsequent syncs are incremental (5-10 minutes)
• Check ETL Health Dashboard for progress
• Don’t interrupt first sync

Business Value

Time Savings

Before Integrations:

• 40 hours to compile audit evidence manually
• Data outdated by audit time
• No proof of real-time compliance

With Integrations:

• 5 minutes to generate audit package
• Evidence auto-collected every 4 hours
• Real-time compliance status

Annual Savings: $24,000 in labor (at $150/hr)

Revenue Opportunities

Integration data powers automatic revenue discovery:

Gap Detection:

• Customer missing EDR? → Huntress integration finds 0 agents
• MFA not enabled? → Microsoft 365 integration finds gaps
• Hardware outdated? → NinjaOne finds devices >5 years old

Opportunity Detection: Automatically identifies missing services, licensing gaps, and upgrades

Customer Proof

Show customers exactly what you’re doing:

Customer Portal Shows:

• Real-time compliance status
• Evidence from integrations
• Services delivering value
• Gaps that need addressing

Example:

“Your 147 endpoints are protected by Huntress EDR. In the last 30 days, we detected and blocked 3 ransomware attempts. This satisfies CIS Control 10.1 and NIST PR.DS-5.”

Next Steps

1. Set Up Your First Integration

   • Start with your RMM (NinjaOne recommended)
   • NinjaOne Setup Guide

2. Add Security Tools

   • Connect EDR platform (Huntress recommended)
   • Huntress Setup Guide

3. Connect Microsoft 365

   • Enable user/license tracking
   • Microsoft 365 Setup Guide

4. Monitor Integration Health

   • Check ETL Dashboard weekly
   • Review sync success rates
   • ETL Monitoring Guide

Questions?

• How does customer auto-matching work?
• What if my integration isn’t listed?
• How do I troubleshoot sync failures?
• Contact Support