TCP SYN state-exhaustion flood
Historical concept · local-technique:syn-flood
Attributed source ↗ · Plaintext record · Complete record and assertions JSON
Incomplete TCP connection attempts can exhaust listener resources.
Connection-state monitoring, SYNcookies or proxies and engineered resource limits.
RFC is informational and describes earlier history;2007is not an invention date. Endpoint state exhaustion differs from bandwidth flooding.
Documented publication credit
RFC4987: TCP SYN Flooding Attacks and Common Mitigations — Wesley Eddy (RFC author and retrospective technical synthesis). This is a publication record, not an origin or invention claim.
Inspect structured metadata and provenance
{
"id": "local-technique:syn-flood",
"title": "TCP SYN state-exhaustion flood",
"type": "Historical concept",
"snapshot": "historical-seed.json",
"source_url": "https://www.rfc-editor.org/info/rfc4987/",
"description": "Incomplete TCP connection attempts can exhaust listener resources.",
"defensive_context": "Connection-state monitoring, SYNcookies or proxies and engineered resource limits.",
"publication": {
"id": "local-publication:syn-flood-milestone",
"entity_type": "Publication",
"title": "RFC4987: TCP SYN Flooding Attacks and Common Mitigations",
"source_url": "https://www.rfc-editor.org/info/rfc4987/",
"publication_date": "2007-08",
"publisher": "RFC Editor",
"credit_display": "Wesley Eddy",
"credit_role": "RFC author and retrospective technical synthesis"
},
"mappings": [
{
"target_id": "ATTACK:enterprise:T1499.001",
"relation": "OS-exhaustion behavior including SYNfloods",
"status": "research-supplied conceptual mapping; target exists in imported taxonomy; semantic review pending"
}
],
"uncertainty": "RFC is informational and describes earlier history;2007is not an invention date. Endpoint state exhaustion differs from bandwidth flooding.",
"rights": "Original concise metadata and linked references; no full paper or payload imported",
"review_status": "Editorial historical seed; conceptual mappings remain explicitly provisional"
}Explicit source assertions (0)
First 80 shown here; the complete set is in this record’s JSON and plaintext. Each relationship retains its source and locator. No inferred relationships are added.