Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21e39926bd8452a

Jump to content

Talk:Attack surface

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 28 days ago by M kuhner in topic Regulatory implications section

Defining Attack Surface

[edit]

@LuisVilla: FYI I think this recent NDSS paper has a more concise definition of the attack surface than what I am currently read here, albeit it *seems* to be for the Linux kernel only... Fedcaster (talk)

@Fedcaster: The definition isn't Linux-only; it is generic. Definitely the best one I've seen in terms of rigor. But it is also incredibly... well, it isn't exactly plain english by any stretch :) Probably a good citation/reference, but not a definition I'd want to try to pull into the article? You're welcome to try, though! -LuisVilla (talk) 18:58, 8 November 2013 (UTC)Reply

Older Notes/Comments

[edit]

It doesn't seem correct to say "how much (damage) can a piece of software do in its default configuration by unauthorized users" - it has nothing to do with "default configuration". One can change the configuration from the default, and now there is new 'attack surface'.

Also, note that the word "damage" (or something like it) is left out of that sentence.

--Rob Cranfill (talk) 15:56, 6 March 2008 (UTC)Reply

This article starts with a very odd definition of Attack Surface. It seems to say the attack surface is the extent of the vulnerabilities in the system, rather than the total of potential places an attack could start. The OWASP definition seems far clearer and more useful, because the whole point is you don't know where the actual vulnerabilities are otherwise you would've fixed them and have "no attack surface" SimonWiseman (talk) 17:46, 30 January 2013 (UTC)Reply

@SimonWiseman:, @Rob Cranfill: FYI, I'm starting to work on this page (Attack Surface); addressed both of your comments but would love more help if you have some cycles. -LuisVilla (talk) 20:35, 30 October 2013 (UTC)Reply

Regulatory implications section

[edit]

This section has multiple problems: It's likely LLM (see WP:AINB § User:Jgellatry); the author was blocked for advertising or promotion and has declared COI with HIPAA regulation; it is purely US-centric; and it gives far more detail than is needed. There's a discussion of this type of section, inserted into many articles very rapidly by the same author, at Wikipedia talk:WikiProject Computer security § Regulatory requirements sections.

I am taking the entire section out based on these considerations. If you revert it I won't contest, but please edit it thoroughly to address the problems above. M kuhner (talk) 13:26, 29 June 2026 (UTC)Reply