Add Kestrel security considerations article#37328
Merged
BrennanConroy merged 4 commits intoJul 16, 2026
Merged
Conversation
Publish a new Learn article covering Kestrel's security considerations, configurable limits, and request-parsing behavior, and add a TOC entry under the Kestrel node. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Spell out 'and' in section headings (replacing '&' and '/') so the OPS-generated bookmarks use clean single-dash anchors, and update the in-page links to match. Resolves the bookmark-not-found build warnings. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
BrennanConroy
marked this pull request as ready for review
July 9, 2026 23:04
BrennanConroy
requested review from
DeagleGross,
halter73,
tdykstra and
wadepickett
July 9, 2026 23:05
wadepickett
reviewed
Jul 10, 2026
wadepickett
reviewed
Jul 10, 2026
wadepickett
approved these changes
Jul 10, 2026
wadepickett
left a comment
wadepickett
left a comment
Contributor
There was a problem hiding this comment.
Looks great! Approved. See my two suggestions inline.
Contributor
|
@tdykstra, watch in case any timely review merge help needed, since I am not available for a week starting today. |
gfoidl
reviewed
Jul 12, 2026
Member
|
cc fyi - @GrabYourPitchforks @blowdart @artl93 |
Contributor
|
🥂 |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Member
Author
|
@tdykstra Need a new approval since a new commit was made. |
DeagleGross
approved these changes
Jul 15, 2026
DeagleGross
left a comment
DeagleGross
left a comment
Member
There was a problem hiding this comment.
Great article, I really like the ordering of story telling here starting from server topology and going into details of specific defence mechanisms.
Left comments, but up to you to react to them. Sorry for taking longer time to review
| | [**HSTS**](#http-strict-transport-security-hsts) | Not enabled | Enable | Enable | [Security Middleware](#security-middleware) | | ||
| | [**Forwarded Headers**](#forwarded-headers) | Not enabled | **Don't enable** | Enable with `KnownProxies` | [Security Middleware](#security-middleware) | | ||
| | [**Rate Limiting**](#rate-limiting) | Disabled | Enable | Enable (app-level) | [Security Middleware](#security-middleware) | | ||
| | [**CORS**](#cors) | Disabled | Configure per API (if needed) | Configure per API (if needed) | [Security Middleware](#security-middleware) | |
Member
There was a problem hiding this comment.
do we want to add a section about Antiforgery?
BrennanConroy
commented
Jul 15, 2026
Co-authored-by: Korolev Dmitry <dmkorolev@microsoft.com> Co-authored-by: Brennan <brecon@microsoft.com>
DeagleGross
approved these changes
Jul 16, 2026
BrennanConroy
deleted the
brennanconroy-kestrel-security-considerations-doc
branch
July 16, 2026 17:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Kestrel has a large surface of security-relevant behaviors, configurable limits, and request-parsing decisions that weren't documented anywhere. This publishes that guidance as a proper Learn article so application developers configuring Kestrel in production and security auditors reviewing its threat surface have a single reference.
What
aspnetcore/fundamentals/servers/kestrel/security-considerations.md, a new article covering trust boundaries and reverse-proxy topologies, transport security (TLS/mTLS), HTTP/1.1, HTTP/2, and HTTP/3 limits, request smuggling and parsing validation, forwarded headers, host filtering, rate limiting, WebSockets, named pipes, monitoring/metrics, and a production security checklist.aspnetcore/toc.yml.Notes for reviewers
<xref:...>cross-references to avoid fabricating unverified API doc IDs, per the repo's guidance. These can be linked later once IDs are confirmed.not-latest-version-without-not-supported-content.mdinclude, which is the required variant for articles targeting>= aspnetcore-8.0.monikerRangeis set to>= aspnetcore-8.0; adjust if a different lower bound is preferred.This content is AI-assisted (
ai-usage: ai-assistedin frontmatter).Internal previews