Sense & compare
Normalize observations. Preserve evidence. Understand what changed in the genome.
A continuously learning cyber-resilience organism
Every organisation has
its own cyber DNA.
Understand your connections. Recognise dangerous change. Remember what worked. Become more resilient with every verified outcome.
Not another dashboard.
An understanding that stays.
blakDNA is not a SIEM, CSPM, scanner, GRC platform, SOC dashboard, or chatbot. It connects their signals to your organisation's evolving context.
Meet the organismThe Security Genome
See relationships.
Not isolated findings.
Assets, identities, privileges, controls, and decisions form a connected picture of what matters and what an attacker could reach.
IdentitiesWorkloadsTrustRepositoriesDataEvidenceControlsDecisions
Inside the genome One permission.
A different risk.
A deployment role gains IAM policy-management rights. The change matters because of the route it may open.
- GitHub repository
- Actions
- AWS deployment role
- IAM policy modification
- Production privilege escalation
Synthetic demonstration. Reachability depends on policy scope, trust, and effective controls.
Understand the pathThe loop never ends
at “finding closed”.
Remember & investigate
Retrieve relevant memory. Test a hypothesis. Challenge the apparent attack path.
Explain & respond
Call out material risk. Capture a human's reason, not just a button press.
Verify & learn
Observe the fix independently. Retain the outcome. Evaluate adaptive antibodies.
A hard boundary
Normal does not
mean secure.
Learning your organisation's habits must never erase security knowledge. A common weakness is still a weakness.
Read the safety modelHermes thinks.
blakDNA remembers.
Scoped reasoning and specialist delegation, supported by deterministic engineering and persistent cyber-specific memory.
Before you connect.
Is blakDNA another SIEM or chatbot?
No. blakDNA maintains a temporal organisation model and persistent cyber memory. It works with security data sources rather than replacing them with a chat interface or another log store.
Does normal behaviour become trusted automatically?
No. Normal and secure remain separate judgements. Repeated unsafe behaviour remains unsafe, even when it is common in the organisation.
Can blakDNA change production controls by itself?
Consequential remediation requires explicit human approval by default. Investigation, recommendations, and verification do not authorize changing IAM, disabling accounts, or deleting infrastructure.
Where does the organisation's data live?
The customer-hosted architecture keeps the application and authoritative PostgreSQL data in the buyer's AWS environment. Hermes receives scoped evidence context through approved interfaces, not unrestricted raw telemetry.