Central capture
Security events and abuse signals are meant to land in one database, with source, time and reason kept together.
One record, not scattered logsCTIAD · Central Threat Intelligence & Abuse Database
CDPGuard detects and protects. CTIAD is the database behind that work: security events and abuse signals in one place, scored so protection systems and reviews can use them.
Role
CDPGuard filters and blocks on the server. CTIAD keeps the record: what was seen, how it relates to other signals, and what score that record carries.
Security events and abuse signals are meant to land in one database, with source, time and reason kept together.
One record, not scattered logsA single request is weak evidence. CTIAD is built so repeated sources, similar paths and matching abuse types can be read as one case.
Context across eventsCollected material is scored so a protection system or an analyst can tell a noisy probe from a source that keeps coming back.
Assessment, not a raw dumpThe point of the database is output: lists, case summaries and material a firewall or an operator can act on.
For protection and reviewWhat sits inside
The facts
Only the properties of the design. A function is described as live only when this site can point at it.
Principles
A signal that is not stored cannot be correlated later.
Address, time and reason stay on the record.
A raw hit is not the same thing as a published indicator.
Publishing a list is one output. It does not replace the database.
External catalogues can be compared. They are not the system.
This public site does not pretend a feed or an integration is running.
Central threat intelligence and abuse data for the CTPF network. Questions go through the contact form.