Light Freshness Edit: ASP.NET - Security topics

[GitHubber17]

This PR contains light freshness updates to 6 articles:

• ASP.NET Core security topics

• Azure Key Vault configuration provider in ASP.NET Core

• ASP.NET Core Data Protection Overview (moniker range=">= aspnetcore-8.0")

• Prevent Cross-Site Scripting (XSS) in ASP.NET Core (moniker range=">= aspnetcore-6.0")

• Safe storage of app secrets in development in ASP.NET Core (moniker range=">= aspnetcore-6.0")
  -- Also updated 2 include files
  -- Deleted 1 image that showed code, moved code into file, removed sensitive data

• Enforce HTTPS in ASP.NET Core (:::moniker range=">= aspnetcore-9.0")
  -- Minor updates to 2 images
  -- In the section Opt-out of HTTPS/HSTS on project creation > Visual Studio, the article
  was using the VS 2019 image. I changed to the VS 2022 image (already in the folder).

  Do you want a VS 2026 version of the image? The UI is updated with more options.

For details, see ADO request 568764.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/security/app-secrets.md	customer intent: As an ASP.NET Core developer, I want to store and retrieve sensitive information during development of my app, so I can ensure my app secrets remain secure.
aspnetcore/security/cross-site-scripting.md	Prevent Cross-Site Scripting (XSS) in ASP.NET Core
aspnetcore/security/data-protection/introduction.md	customer intent: As a developer, I want to learn about data protection and design principles of the ASP.NET Core Data Protection APIs, so I can use the APIs in my apps.
aspnetcore/security/enforcing-ssl.md	Enforce HTTPS in ASP.NET Core
aspnetcore/security/index.md	aspnetcore/security/index
aspnetcore/security/key-vault-configuration.md	customer intent: As an ASP.NET Core developer, I want to use the Azure Key Vault configuration provider, so I can load app configuration values from Key Vault secrets at runtime.

[GitHubber17]

Close/Reopen PR per Build Validation - error seemingly not related to any file in this PR:

[GitHubber17]

Hi @tdykstra - Refreshed topics ready for review. Please see my notes to address in the top comment. Thanks

The Build Warnings apply to files not in this PR:

Cc @wadepickett @BillWagner @cmastr

[wadepickett]

@GitHubber17, looks great! I added a few suggestions inline. Minor stuff.

[wadepickett]

Re: build warnings.
@GitHubber17, Thanks for the heads up. Yes, these were not part of this PR. I'll go track it down. It should not hold up your merge.

[GitHubber17]

@wadepickett - Updates applied: edits and format.

Did you see my question in the top comment about the VS 2026 version of the image?

[wadepickett]

RE:
"Do you want a VS 2026 version of the image? "

You could do it and select the same .NET target it had before (8?).
The code in this article from what I see is using .NET 6.x templates and structures. The article needs to be technically updated. I think updating only the screenshot at this point wouldn't help.

@tdykstra, this articles should have a new tracking issue for updating its code samples.

[GitHubber17]

Close/Reopen for fresh build to clear warnings for external files.

[wadepickett]

Approved, but will wait for Tom to have a chance to review before merging. Good work, thanks!