Lodemark
Sign inBook a walkthrough
Integrations

It has to land where the work already happens

24 connectors across six categories. Discovery reads, remediation writes into the tracker each team already uses, and everything else is available through a documented REST API.

Categories
  • Cloud & infrastructureRead-only discovery across accounts, projects and subscriptions.
  • SIEM & data pipelineStream findings, path changes and asset events where you already look.
  • Ticketing & ITSMCreate owned, time-boxed work in the tracker teams already use.
  • DevOps & sourceCatch exposure before it ships, and attribute it to the change that caused it.
  • IdentityEntitlement graphs, federation topology and joiner-mover-leaver signal.
  • Alerting & commsRoute the handful of events that need a human, and nothing else.
Amazon Web Services

Organisation-wide discovery for 180+ resource types.

inbound
Microsoft Azure

Subscription, resource-group and entitlement inventory.

inbound
Google Cloud

Project, IAM and workload discovery with asset feeds.

inbound
Kubernetes

Cluster, namespace and admission posture.

inbound
Cloudflare

DNS zones, WAF rules and edge certificate inventory.

inbound
Terraform Cloud

Plan-time exposure checks and drift attribution.

bidirectional
GitHub

Repository, workflow and OIDC claim mapping.

bidirectional
GitLab

Pipeline identity and registry provenance.

bidirectional
Snyk

Dependency findings correlated onto reachable workloads.

inbound
Splunk

Stream findings and path changes as structured events.

outbound
Microsoft Sentinel

Analytics rules keyed to exposure and path state.

outbound
Elastic Security

Index asset context alongside detection data.

outbound
Chronicle

Entity enrichment for investigation timelines.

outbound
Jira

Owned remediation tickets with SLA sync both ways.

bidirectional
ServiceNow

Change and incident records with CMDB reconciliation.

bidirectional
Linear

Engineering-native remediation work items.

bidirectional
Okta

Federation topology, groups and factor coverage.

inbound
Microsoft Entra ID

Conditional access, app registrations and role graph.

inbound
Ping Identity

Policy and session context for federated tenants.

inbound
HashiCorp Vault

Secret lease telemetry and rotation posture.

inbound
Slack

Channel routing for path changes and SLA breaches.

outbound
Microsoft Teams

Adaptive cards for triage and acknowledgement.

outbound
PagerDuty

Page only when a path reaches a Core asset.

outbound
Webhooks & API

Signed webhooks and a documented REST API for everything else.

bidirectional
API

Everything in the console is in the API

Assets, findings, paths, remediation records and the change ledger. Stable entity identifiers, cursor pagination, signed webhooks and a documented rate limit. No proprietary export format.

Read the documentation
List live paths reaching a crown-jewel asset
# List live attack paths that terminate at a crown jewel
curl -s https://api.lodemark.com/v1/paths \
  -H "Authorization: Bearer $LODEMARK_TOKEN" \
  -G --data-urlencode "status=live" \
     --data-urlencode "destination.crown_jewel=true"
Next step

Missing a connector you need?

Tell us which one. Connectors that several customers need get built on the fortnightly release train, and the API covers the rest in the meantime.

Request a connectorSee the API documentation

Illustrative product data. Nothing on this site performs a live scan.