mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
updates
This commit is contained in:
Paolo Matarazzo
parent
f13f64329d
commit
3266f8316b
@ -1,26 +0,0 @@
|
||||
---
|
||||
title: Windows security features and edition requirements
|
||||
description: Learn about Windows edition requirements for the feature included in Windows.
|
||||
ms.prod: windows-client
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
- tier3
|
||||
ms.topic: conceptual
|
||||
ms.date: 05/04/2023
|
||||
appliesto:
|
||||
- ✅ <a href=/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
ms.technology: itpro-security
|
||||
---
|
||||
|
||||
# Windows security features and edition requirements
|
||||
|
||||
This article lists the security features that are available in Windows, and the Windows editions that support them.
|
||||
|
||||
> [!NOTE]
|
||||
> The **Windows edition** requirements listed in the following table may be different from the **licensing** requirements. If you're looking for licensing requirements, see [Windows security features and licensing requirements](security-features-licensing-requirements.md).
|
||||
|
||||
[!INCLUDE [_edition-requirements](../../../includes/licensing/_edition-requirements.md)]
|
||||
|
||||
For more information about Windows licensing, see [Windows Commercial Licensing overview](/windows/whats-new/windows-licensing).
|
||||
@ -1,26 +0,0 @@
|
||||
---
|
||||
title: Windows security features and licensing requirements
|
||||
description: Learn about Windows features and licensing requirements for the feature included in Windows.
|
||||
ms.prod: windows-client
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
- tier3
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/24/2023
|
||||
appliesto:
|
||||
- ✅ <a href=/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
ms.technology: itpro-security
|
||||
---
|
||||
|
||||
# Windows security features and licensing requirements
|
||||
|
||||
This article lists the security features that are available in Windows, and the licensing requirements to use them.
|
||||
|
||||
> [!NOTE]
|
||||
> The **licensing** requirements listed in the following table may be different from the **Windows edition** requirements. If you're looking for Windows edition requirements, see [Windows security features and edition requirements](security-features-edition-requirements.md).
|
||||
|
||||
[!INCLUDE [_licensing-requirements](../../../includes/licensing/_licensing-requirements.md)]
|
||||
|
||||
For more information about Windows licensing, see [Windows Commercial Licensing overview](/windows/whats-new/windows-licensing).
|
||||
@ -4,7 +4,7 @@ description: Learn about Windows licensing and edition requirements for the feat
|
||||
ms.collection:
|
||||
- tier2
|
||||
ms.topic: conceptual
|
||||
ms.date: 06/13/2023
|
||||
ms.date: 06/15/2023
|
||||
appliesto:
|
||||
- ✅ <a href=/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
ms.author: paoloma
|
||||
@ -20,11 +20,11 @@ Select one of the two tabs to learn about licensing requirements to use the secu
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/windows-os.svg" border="false"::: **Licensing requirements**](#tab/licensing)
|
||||
|
||||
[!INCLUDE [licensing-requirements](../../../includes/licensing/_licensing-requirements.md)]
|
||||
[!INCLUDE [licensing-requirements](../../includes/licensing/_licensing-requirements.md)]
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/windows-os.svg" border="false"::: **Edition requirements**](#tab/edition)
|
||||
|
||||
[!INCLUDE [_edition-requirements](../../../includes/licensing/_edition-requirements.md)]
|
||||
[!INCLUDE [_edition-requirements](../../includes/licensing/_edition-requirements.md)]
|
||||
|
||||
---
|
||||
|
||||
@ -1,18 +1,13 @@
|
||||
---
|
||||
title: Windows security foundations
|
||||
description: Get an overview of security foundations, including the security development lifecycle, common criteria, and the bug bounty program.
|
||||
ms.reviewer:
|
||||
ms.topic: article
|
||||
ms.author: paoloma
|
||||
author: paolomatarazzo
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-security
|
||||
ms.date: 12/31/2017
|
||||
ms.topic: conceptual
|
||||
ms.date: 06/15/2023
|
||||
---
|
||||
|
||||
# Windows security foundations
|
||||
|
||||
Microsoft is committed to continuously invest in improving our software development process, building highly secure-by-design software, and addressing security compliance requirements. At Microsoft, we embed security and privacy considerations from the earliest life-cycle phases of all our software development processes. We build in security from the ground for powerful defense in today’s threat environment.
|
||||
Microsoft is committed to continuously invest in improving our software development process, building highly secure-by-design software, and addressing security compliance requirements. At Microsoft, we embed security and privacy considerations from the earliest life-cycle phases of all our software development processes. We build in security from the ground for powerful defense in today's threat environment.
|
||||
|
||||
Our strong security foundation uses Microsoft Security Development Lifecycle (SDL) Bug Bounty, support for product security standards and certifications, and Azure Code signing. As a result, we improve security by producing software with fewer defects and vulnerabilities instead of relying on applying updates after vulnerabilities have been identified.
|
||||
|
||||
@ -20,7 +15,7 @@ Use the links in the following table to learn more about the security foundation
|
||||
|
||||
| Concept | Description |
|
||||
|:---|:---|
|
||||
| FIPS 140-2 Validation | The Federal Information Processing Standard (FIPS) Publication 140-2 is a U.S. government standard. FIPS is based on Section 5131 of the Information Technology Management Reform Act of 1996. It defines the minimum security requirements for cryptographic modules in IT products. Microsoft maintains an active commitment to meeting the requirements of the FIPS 140-2 standard, having validated cryptographic modules against it since it was first established in 2001. <br/><br/>Learn more about [FIPS 140-2 Validation](threat-protection/fips-140-validation.md). |
|
||||
| Common Criteria Certifications | Microsoft supports the Common Criteria certification program, ensures that products incorporate the features and functions required by relevant Common Criteria Protection Profiles, and completes Common Criteria certifications of Microsoft Windows products. <br/><br/>Learn more about [Common Criteria Certifications](threat-protection/windows-platform-common-criteria.md). |
|
||||
| Microsoft Security Development Lifecycle | The Security Development Lifecycle (SDL) is a security assurance process that is focused on software development. The SDL has played a critical role in embedding security and privacy in software and culture at Microsoft.<br/><br/>Learn more about [Microsoft SDL](threat-protection/msft-security-dev-lifecycle.md).|
|
||||
| FIPS 140-2 Validation | The Federal Information Processing Standard (FIPS) Publication 140-2 is a U.S. government standard. FIPS is based on Section 5131 of the Information Technology Management Reform Act of 1996. It defines the minimum security requirements for cryptographic modules in IT products. Microsoft maintains an active commitment to meeting the requirements of the FIPS 140-2 standard, having validated cryptographic modules against it since it was first established in 2001. <br/><br/>Learn more about [FIPS 140-2 Validation](../threat-protection/fips-140-validation.md). |
|
||||
| Common Criteria Certifications | Microsoft supports the Common Criteria certification program, ensures that products incorporate the features and functions required by relevant Common Criteria Protection Profiles, and completes Common Criteria certifications of Microsoft Windows products. <br/><br/>Learn more about [Common Criteria Certifications](../threat-protection/windows-platform-common-criteria.md). |
|
||||
| Microsoft Security Development Lifecycle | The Security Development Lifecycle (SDL) is a security assurance process that is focused on software development. The SDL has played a critical role in embedding security and privacy in software and culture at Microsoft.<br/><br/>Learn more about [Microsoft SDL](../threat-protection/msft-security-dev-lifecycle.md).|
|
||||
| Microsoft Bug Bounty Program | If you find a vulnerability in a Microsoft product, service, or device, we want to hear from you! If your vulnerability report affects a product or service that is within scope of one of our bounty programs below, you could receive a bounty award according to the program descriptions.<br/><br/>Learn more about the [Microsoft Bug Bounty Program](https://www.microsoft.com/en-us/msrc/bounty?rtc=1). |
|
||||
@ -1,6 +1,6 @@
|
||||
items:
|
||||
- name: Overview
|
||||
href: ../security-foundations.md
|
||||
href: index.md
|
||||
- name: Microsoft Security Development Lifecycle
|
||||
href: ../threat-protection/msft-security-dev-lifecycle.md
|
||||
- name: Certification
|
||||
|
||||
@ -9,11 +9,7 @@
|
||||
- name: Zero Trust and Windows
|
||||
href: zero-trust-windows-device-health.md
|
||||
- name: Security features licensing and edition requirements
|
||||
href: introduction/licensing-and-edition-requirements.md
|
||||
- name: Security features and edition requirements
|
||||
href: introduction/security-features-edition-requirements.md
|
||||
- name: Security features and licensing requirements
|
||||
href: introduction/security-features-licensing-requirements.md
|
||||
href: licensing-and-edition-requirements.md
|
||||
- name: Hardware security
|
||||
href: hardware-security/toc.yml
|
||||
- name: Operating system security
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user