01
What the product does
Available sources and fields depend on licensing, legal basis, privacy approval, region and the customer purpose.
Controlled Guardian intelligence capability
Bring approved entity and cyber-intelligence context into one auditable review.
Guardian Intelligence can combine approved entity, relationship, screening and cyber-intelligence sources into a case workflow where evidence and disposition remain under human review.
Australian data residency
Guardian for Australian customers is built, operated and hosted in Australia. All Guardian customer and platform data, including backups and recovery copies, is maintained and stored within Australia.
Approved sources and purposeEntity and relationship contextCyber-intelligence signalsHuman review and audit history
Buyer decision summary
Know what Guardian Intelligence does, what the customer sees and what Damocles is responsible for before activation.
Guardian retains the approved source snapshot, identifiers, possible-match context, evidence, reviewer, date, rationale, disposition, follow-up and supersession history according to the approved purpose.
The proposal identifies licensed sources, entity types, monitored quantities, refresh cadence, case volume, fields, retention, reviewers, analyst support, reporting and customer purpose.
Automated matches are signals for review. Guardian must not present a possible match as proof that a person committed an offence, is sanctioned, is politically exposed or is criminally associated.
02
What the customer sees
General users do not receive unrestricted intelligence or sensitive source access.
03
What Damocles manages
Legal advice, identity verification and investigative conclusions remain separate unless specifically authorised and supported.
The operational problem
Risk changes when an entity, relationship or cyber signal changes, but automated matches must not become unsupported conclusions.
Traditional screening and cyber-intelligence sources can produce useful context about people, organisations, relationships, identifiers, exposure, malicious infrastructure or other approved risk signals. The difficulty is preserving provenance, resolving possible matches and ensuring a person reviews the evidence.
Guardian Intelligence is a correlation and decision-support layer. It creates explainable cases and audit history while keeping source licensing, legal basis, privacy, retention and disposition under controlled authority.
01
Build a connected entity view
Normalise approved people, organisations, identifiers, relationships and cyber indicators around the subject being reviewed.
02
Detect material change
Use refreshed source snapshots or approved monitoring to identify new context requiring review.
03
Keep the decision human and auditable
Retain source, evidence, reviewer, rationale, disposition, date and supersession history.
Product capability
Approved intelligence sources brought into one controlled review workflow.
Available sources and fields depend on licensing, legal basis, privacy approval, region and the customer purpose.
EN
Entity profiles
Create normalised people, organisation, identifier and relationship context for approved review purposes.
RS
Relationship mapping
Record approved ownership, control, association and linked-entity context with source provenance.
SC
Screening context
Use approved sanctions, politically exposed person, adverse-media or corporate sources where licensed.
CI
Cyber-intelligence context
Add approved credential exposure, malicious infrastructure, threat or other cyber signals where available.
CA
Cases and disposition
Turn potential matches and changes into cases requiring evidence and authorised human review.
AU
Audit and provenance
Retain source, snapshot, evidence, reviewer, date, rationale, disposition and supersession history.
What Damocles manages
Damocles can manage source integration, case quality and analyst review according to the approved service.
Legal advice, identity verification and investigative conclusions remain separate unless specifically authorised and supported.
SP
Source and purpose onboarding
Confirm licensed sources, customer purpose, legal basis, privacy, reviewers, fields and retention.
EM
Entity mapping
Normalise approved identifiers and relationships without treating fuzzy similarity as proof.
QM
Quality management
Review duplicate entities, source conflicts, stale context, provenance and missing evidence.
CR
Case review support
Assist authorised analysts with evidence gathering, workflow and disposition where contracted.
CM
Change monitoring
Refresh approved sources and create review work when material context changes.
AR
Audit reporting
Report cases, source use, review age, disposition and unresolved evidence according to authority.
Operating lifecycle
From approved source data to a reviewable and auditable decision.
Source use begins only after licensing, legal basis, privacy, purpose and retention are approved.
01
Define purpose
Confirm entity type, business purpose, legal basis, approved sources and authorised reviewers.
02
Collect approved data
Retrieve or receive the permitted source snapshot and identifiers.
03
Correlate
Normalise entities, names, relationships and cyber indicators without treating similarity as proof.
04
Create a case
Open a review case when a possible match or material change requires human assessment.
05
Review and disposition
The authorised reviewer records evidence, rationale, conclusion and required follow-up.
06
Monitor and audit
Retain provenance and create new review work when approved context changes.
Common use cases
Potential Guardian Intelligence use cases subject to approved purpose and source authority.
Each use case requires separate review of licensing, privacy, legal basis, fields and human disposition.
ED
Entity due diligence
Bring approved corporate, ownership, relationship and source context into one case record.
CM
Change monitoring
Identify material changes to an approved entity or relationship requiring reviewer attention.
CI
Cyber-intelligence enrichment
Add approved cyber indicators or exposure context to a security or risk review.
IR
Investigation support
Use authorised entity and cyber context to support a security investigation without replacing analyst judgement.
MS
Provider analyst workflow
Allow authorised provider analysts to review customer-scoped cases under explicit permissions.
AU
Audit and governance
Retain who reviewed what source, when, why and what disposition was recorded.
Operating model
How Guardian Intelligence is onboarded, integrated, evidenced and scoped commercially.
These details remain explicit before activation, but are grouped into one operating view so buyers can review the responsibilities without working through four separate page sections.
ON
Onboarding and implementation
Onboarding begins with purpose, authority and source governance—not data ingestion. The customer defines the approved business purpose, entity types, legal basis, privacy requirements, licensed sources, authorised reviewers, evidence, retention, disposition and escalation. Damocles does not enable a source simply because technical access is possible. Sample entities and cases are reviewed to validate identifier handling, possible-match presentation, source provenance, evidence, reviewer workflow, role access and reporting before broader use. Go-live includes source and field registers, reviewer authority, case states, audit, retention, change monitoring, support and a documented process for incorrect, disputed or superseded information.
IN
Connector and integration model
Each intelligence connector is approved for a purpose, field set and review model. A supported connector must preserve source provenance, snapshot date, entity identifiers, field authority, permitted use, retrieval constraints and safe error state. Guardian does not treat source similarity or a connector result as a final legal or identity conclusion. New sources are reviewed for licensing, terms, legal basis, privacy, field quality, region, retention, explainability, dispute handling, supportability and commercial impact. Guardian Intelligence does not internally provide facial recognition, biometric verification, document capture or identity-document retention unless a future separately approved capability explicitly adds those functions.
EV
Data, evidence and reporting
Every material case retains source provenance, reviewer rationale and disposition history. Guardian retains the approved source snapshot, identifiers, possible-match context, evidence, reviewer, date, rationale, disposition, follow-up and supersession history according to the approved purpose. Access remains role and customer scoped. Sensitive source fields, restricted records and analyst-only material are not exposed to general users or public pages. Reports distinguish source facts, possible matches, reviewer judgement and unresolved uncertainty rather than merging them into an opaque risk score.
CM
Commercial unit and responsibilities
Commercial scope follows approved sources, monitored entities, review volume and analyst service. The proposal identifies licensed sources, entity types, monitored quantities, refresh cadence, case volume, fields, retention, reviewers, analyst support, reporting and customer purpose. Source fees, specialist analyst review, custom correlation, investigation and expanded monitoring can be separate commercial inputs. The customer owns legal basis, purpose, reviewer authority and final decisions. Damocles owns the integration and service activities listed in the schedule.
Frequently asked questions
Questions buyers ask about Guardian Intelligence.
The exact answer is confirmed in the proposal and package schedule, but these points should be understood before activation.
Q1
Does Guardian make automatic sanctions or criminal decisions?
No. Automated signals create review work. An authorised human reviewer must assess evidence and record disposition.
Q2
Can any data source be connected?
No. Licensing, legal basis, privacy, fields, provenance and supportability must be approved first.
Q3
Does it verify identity documents?
Not as part of the current intelligence-correlation product. Identity-document and biometric capability would require separate approval.
Q4
Can cyber intelligence be included?
Yes where the source, purpose, fields, licensing and reviewer workflow are approved.
Q5
Can an MSP or provider review cases?
Only where explicit customer authority, role permissions and purpose permit provider review.
Q6
How are incorrect records handled?
The workflow must support review, dispute, correction, supersession and retained audit history according to the approved policy.
Scope and boundaries
Guardian Intelligence is decision support and never proof of criminal, sanctions, political or identity status by itself.
Automated matches are signals for review. Guardian must not present a possible match as proof that a person committed an offence, is sanctioned, is politically exposed or is criminally associated.
Source licensing, legal basis, privacy, retention, reviewer authority and customer purpose must be approved before live use.
Guardian Intelligence does not replace legal advice, specialist investigation or human judgement.
Take the next practical step
Define the entities, sources and decisions that require auditable intelligence context.
We will map the approved purpose, sources, licensing, privacy, reviewers, evidence, case workflow and change monitoring.