01
Continuous audit evidence
Logging and monitoring controls (ISO 27001 A.8.15, A.8.16, SOC 2 CC7) are proven by Splunk data, with no screenshots or manual exports.
Cookie policy
We use cookies to improve your experience and analyze traffic. Choose “Manage preferences” to customize, or see our Privacy Policy for details.
Splunk connector
Splunk sees everything that happens across your environment. Domyno turns it into governance: up-to-date risks, continuously proven compliance, tracked actions and executive reporting.
Illustrative scenario: each step triggers automatically, a human validates.
Splunk · correlated alert
Brute force on admin accounts
47 failures · 3 accounts · 6 min
notable · urgency: highAsset and owner
Domain controller AD-PROD-01 · owner: CIO
Risk recalculated
Privileged identity compromise: 9 → 14 / 25
Controls impacted
ISO 27001 A.8.16 · NIS2 Art. 21 · DORA ICT incident
Remediation action
Enforce MFA on admin accounts · assigned · D+7
Executive dashboard
“Detect” maturity and exposure updated
Back into Splunk (HEC)
sourcetype=domyno:governance · action, decision, due date
Illustrative example
01
Logging and monitoring controls (ISO 27001 A.8.15, A.8.16, SOC 2 CC7) are proven by Splunk data, with no screenshots or manual exports.
02
A major incident becomes a structured file: timeline, affected assets, impact, ready for the 24 h and 72 h deadlines.
03
Risk likelihood moves with what Splunk observes. The register stays alive instead of being reviewed once a year.
04
Domyno matches the asset inventory against Splunk sources and shows which critical assets send no logs.
Splunk data also serves the CISO, risk, compliance and the executive committee.
Splunk becomes the evidence source for compliance, and harder to replace.
For Splunk partners and customers: detection and governance in one approach.
Through the Splunk REST API and saved searches. Nothing is written to Splunk.
Domyno only retrieves the indicators that matter for governance.
Your cloud of choice, any region, or on premises.
Under the hood
Splunk brings the signals, Domyno governs them, and can send its decisions back into Splunk.
Risk register · Compliance · Executive dashboard
Indicative examples, adapted to your environment.
SPL · Detection coverage
| tstats count latest(_time) as last_seen where index=* by host
| eval silent_h=round((now()-last_seen)/3600,1)
| where silent_h > 24What Domyno does with it
Matched against the Domyno inventory: silent critical assets surface as an A.8.16 control gap.
| CIM data model | Domyno module | Controls |
|---|---|---|
| Authentication | Assets & access | ISO A.8.5 · NIS2 Art. 21 (i) · DORA Art. 9 |
| Change | Documentation & compliance | ISO A.8.32 · DORA Art. 9 |
| Network Traffic | Risk analysis | ISO A.8.20 · NIS2 Art. 21 (e) |
| Vulnerabilities | Risk analysis | ISO A.8.8 · NIS2 Art. 21 (e) · DORA Art. 8 |
| Endpoint | Assets & access | ISO A.8.1 · A.8.7 |
Authentication
Authentication token, dedicated read-only role, srchIndexesAllowed limited to the relevant indexes.
Calls
REST API (port 8089), saved searches through /services/search/jobs, scheduled (e.g. 15 min) or triggered by an alert action.
Compatibility
Splunk Cloud Platform and Splunk Enterprise 9.x. Enterprise Security and SOAR optional.
Data
Aggregated results and metadata only, no raw events. Every call is logged.
Deployment
SaaS in the region of your choice, or on premises next to Splunk.
No. Splunk detects and investigates. Domyno builds on that data to govern risk, compliance and decisions.
Yes, both, through the Splunk REST API, including on-premises Splunk Enterprise.
No. Domyno reuses your existing alerts and searches, and can suggest new ones to close gaps.
Connecting takes a few hours with a read-only service account; the rest is configured with our experts.
No extra ingestion from Domyno. Searches are scheduled, time-bounded and favour tstats on accelerated data models.
Not today: the integration uses the REST API. A Splunkbase app is a possible next step.
Yes, each instance is declared as a separate source and attached to the right scope.
30 minutes with a co-founder, on your own context.
Book a meeting