Record entry Β· Cybersecurity
Active Directory
What is happening now
Cannot measure: the record's node for this name could not be read, so its claims are not known here.
How well we know this
Cannot measure: No entity labelled "active-directory" in the record at 2026-10-10T19:00:35.865848+00:00. Try search_entities, or GET /api/signals..
Why this name is on the record
Active Directory was added automatically on 10 Oct 2026 after 21 mentions across 8 sources over 16 days. 81% of that coverage came from a single subject area.
The counts themselves: counted automatically from tracked coverage on 10 Oct 2026
Reported alongside Active Directory
The neighbourhood is not yet read for this page.
For developers
GET https://api.signalbureau.ai/api/registry?slug=active-directory
{
"slug": "active-directory",
"state": "active",
"detail": {
"state": "active",
"source": "ontology",
"label": "active directory",
"promotedAt": "2026-10-10",
"category": "cybersecurity",
"evidence": {
"mentions": 21,
"sources": 8,
"days": 16,
"concentration": 0.81,
"standAloneShare": 0.792
}
}
}The record behind this page, as data. The live response also carries the registry date and version.
Walk the record from Active Directory
This name is not in the walkable record yet: the entity graph does not carry it at this cutoff.
The coverage behind it
- 3 Oct 2026
SecurityWeek
Fortra Patches Critical Vulnerabilities in BoKS (opens the original article)
No trend and no market price are shown because neither has been measured for Active Directory yet. Informational only, not advice. As of 10 Oct 2026.