Integrations and deployment

Connect authorised evidence without blurring tenant boundaries.

KMayer supports API connections, authorised exports and scoped collection components. A provider is not treated as live until authorisation is saved, connection tests pass and the source completes validation.

Connection modes

Choose the least invasive supported path.

API connection

Read-only or least-privilege access is requested for the approved tenant, account, subscription, repository or project boundary.

Recorded evidence

Secret Manager reference; authorised scopes; tenant and account boundary; authoriser; timestamp.

Authorised export

A customer-approved export is parsed, normalised and bound to the organisation and source without turning the file into a live connection.

Recorded evidence

Export provenance; schema version; import time; integrity hash; accepted record count; field-loss result.

Sensor or appliance

A separately approved deployment collects only the agreed scope and reports health, freshness and collection boundaries.

Recorded evidence

Deployment identity; permitted networks; collection scope; health; last successful evidence receipt.

Provider directory

Review the account, boundary and supported evidence path before authorising a source.

These entries describe supported source contracts. They do not mean that a customer source is connected or that KMayer holds its credentials.

12 source contracts shown

ProviderRequired accountLeast-privilege boundaryAPI or authorised exportFreshness and limits
AzureMicrosoft Entra tenant and selected Azure subscriptions.Reader on selected subscriptions; Security Reader only when Defender for Cloud findings are included.Azure Resource Manager API; Azure Resource Graph JSON or CSV.Full and incremental sync after authorisation; provider quotas and pagination apply.
Microsoft Entra IDMicrosoft Entra tenant with an administrator able to grant consent.Directory.Read.All, User.Read.All, Group.Read.All, Application.Read.All and AuditLog.Read.All.Microsoft Graph API; Graph JSON or sign-in and audit CSV.Full and incremental sync after authorisation; provider quotas and pagination apply.
AWSAWS Organizations management account or selected member accounts.SecurityAudit or a narrower read-only equivalent; List and Describe for selected accounts and regions.AWS STS and Config APIs; Config snapshot or Security Hub findings JSON.Full and incremental sync after authorisation; provider quotas and pagination apply.
Google CloudGoogle Cloud organisation or explicitly selected projects.Cloud Asset Viewer and Browser; Security Center Findings Viewer only when findings are included.Cloud Asset and Security Command Center APIs; authorised JSON exports.Full and incremental sync after authorisation; provider quotas and pagination apply.
CloudflareCloudflare account with explicitly selected zones.Read-only account, zone, DNS, SSL certificate and zone-settings permissions for the selected boundary.Cloudflare API; account, zone, DNS, SSL and certificate metadata export.Full and incremental sync after authorisation; provider quotas and pagination apply.
GitHubGitHub organisation with selected repositories.Read-only GitHub App: metadata, members, contents, security events and Dependabot alerts.GitHub API; organisation and repository JSON or SARIF 2.1.0.Full and incremental sync after authorisation; provider quotas and pagination apply.
Microsoft SentinelAzure tenant, subscription and selected Log Analytics workspaces.Microsoft Sentinel Reader and Log Analytics Reader on selected workspaces.Azure and Log Analytics APIs; incidents JSON or query CSV.Full and incremental sync after authorisation; provider quotas and pagination apply.
ServiceNowServiceNow instance with a dedicated integration identity.Read-only ACLs for approved CMDB, incident and change-request fields; no admin or write roles.ServiceNow Table API; table JSON or CMDB CSV.Full and incremental sync after authorisation; provider quotas and pagination apply.
JiraAtlassian Cloud site with explicitly selected Jira projects.Read-only Jira work, user and project scopes; offline access only for approved refresh.Jira Cloud API; authorised issues CSV or JSON.Full and incremental sync after authorisation; provider quotas and pagination apply.
CMDBAuthorised CMDB instance and read-only integration identity.Read-only assets, relationships and owners for approved classes and tables.Approved CMDB API; normalised JSON or RFC 4180 CSV.Full and incremental sync after authorisation; provider quotas and pagination apply.
Vulnerability sourceAuthorised vulnerability platform or approved authoritative feed bound to the asset scope.Read-only assets, findings, scans and remediations for approved business units, groups or tags.Approved source API, CISA KEV, FIRST EPSS or NVD; JSON, CSV or SARIF 2.1.0.Source freshness and publication time remain visible; quotas and feed release schedules apply.
Threat intelligence sourceAuthorised TAXII collection, threat-intelligence tenant or approved authoritative feed.Read-only collections, objects and indicators for the approved source boundary.TAXII 2.1 or approved CISA, CVE, FIRST, NVD and Ubuntu OSV feeds; STIX 2.1 JSON.Source freshness and publication time remain visible; quotas and feed release schedules apply.

Validation sequence

Authorisation is only the beginning of source validation.

  1. Review requirements and approve the exact boundary.
  2. Save a Secret Manager reference or authorised export.
  3. Test connection and permissions.
  4. Run full and incremental ingestion.
  5. Validate deletion, revocation, retry and recovery.
  6. Measure fidelity, field loss, duplicates and evidence hashes.

Operational boundary

Provider state remains explicit.

  • No authorisation saved means no live connection exists.
  • An authorised export remains a point-in-time import, not a continuous connection.
  • API permissions stay read-only or least privilege for the selected boundary.
  • Source freshness, field loss, duplicate rate and evidence hashes remain measurable.

Entitlement and outputs

Know what a connected source unlocks.

A provider connection is enabled only for capabilities included in the customer’s active server-side entitlement. Connecting a source does not expand licensed asset capacity or add capabilities that were not purchased.

Review plan inclusion

See a sample delivered output

Customer delivery boundary

Entitlement controls what enters the private workspace.

  • Before purchase, review the capability map and licensing page for inclusion, counting and prerequisites.
  • After entitlement and source validation, accepted evidence is available only inside the verified tenant workspace.
  • Customer outputs can include the scoped dashboard, evidence records, prioritised actions, reports and audited exports supported by the active plan.
  • Adding a new source or capability requires an approved scope change; it never reuses another tenant’s authorisation.

Deployment boundary

Connection readiness is not live evidence.

Availability depends on the customer environment, approved permissions, source API or export support, and a successful validation run.

Review capability coverage
KMayer - IT Service Provider
Privacy Policy

Our website is committed to protecting your privacy. We collect and process data to enhance your experience, such as recognizing you when you return and understanding how you interact with our content. Your information is used responsibly to ensure that our services remain valuable, secure, and tailored to your needs. For a detailed explanation of how we handle and protect your data, please refer to our Privacy Policy