Skip to content

Commit ef80d40

Browse files
Merge pull request #223964 from TerryLanfear/sec-220113
Freshness update
2 parents ea4f489 + cc7af01 commit ef80d40

File tree

2 files changed

+13
-14
lines changed

2 files changed

+13
-14
lines changed

articles/security/fundamentals/feature-availability.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: terrylan
66
ms.service: security
77
ms.custom: ignite-2022
88
ms.topic: reference
9-
ms.date: 12/30/2021
9+
ms.date: 01/13/2023
1010
---
1111

1212
# Cloud feature availability for commercial and US Government customers
@@ -505,11 +505,11 @@ The following table displays the current Microsoft Defender for IoT feature avai
505505

506506
## Azure Attestation
507507

508-
Microsoft Azure Attestation is a unified solution for remotely verifying the trustworthiness of a platform and integrity of the binaries running inside it. The service receives evidence from the platform, validates it with security standards, evaluates it against configurable policies, and produces an attestation token for claims-based applications (e.g., relying parties, auditing authorities).
508+
Microsoft Azure Attestation is a unified solution for remotely verifying the trustworthiness of a platform and integrity of the binaries running inside it. The service receives evidence from the platform, validates it with security standards, evaluates it against configurable policies, and produces an attestation token for claims-based applications (e.g., relying parties, auditing authorities).
509509

510510
Azure Attestation is currently available in multiple regions across Azure public and Government clouds. In Azure Government, the service is available in preview status across US Gov Virginia and US Gov Arizona.
511511

512-
For more information, see Azure Attestation [public documentation](../../attestation/overview.md).
512+
For more information, see Azure Attestation [public documentation](../../attestation/overview.md).
513513

514514
| Feature | Azure | Azure Government |
515515
|--|--|--|

articles/security/fundamentals/physical-security.md

Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -4,16 +4,15 @@ description: The article describes what Microsoft does to secure the Azure datac
44
services: security
55
documentationcenter: na
66
author: TerryLanfear
7-
manager: barbkess
8-
editor: TomSh
7+
manager: rkarlin
98

109
ms.assetid: 61e95a87-39c5-48f5-aee6-6f90ddcd336e
11-
ms.service: information-protection
12-
ms.subservice: aiplabels
10+
ms.service: security
11+
ms.subservice: security-fundamentals
1312
ms.topic: article
1413
ms.tgt_pltfrm: na
1514
ms.workload: na
16-
ms.date: 07/10/2020
15+
ms.date: 01/13/2023
1716
ms.author: terrylan
1817

1918
---
@@ -24,7 +23,7 @@ This article describes what Microsoft does to secure the Azure infrastructure.
2423
## Datacenter infrastructure
2524
Azure is composed of a [globally distributed datacenter infrastructure](https://azure.microsoft.com/global-infrastructure/), supporting thousands of online services and spanning more than 100 highly secure facilities worldwide.
2625

27-
The infrastructure is designed to bring applications closer to users around the world, preserving data residency, and offering comprehensive compliance and resiliency options for customers. Azure has 58 regions worldwide, and is available in 140 countries/regions.
26+
The infrastructure is designed to bring applications closer to users around the world, preserving data residency, and offering comprehensive compliance and resiliency options for customers. Azure has over 60 regions worldwide, and is available in 140 countries/regions.
2827

2928
A region is a set of datacenters that is interconnected via a massive and resilient network. The network includes content distribution, load balancing, redundancy, and [data-link layer encryption by default](encryption-overview.md#encryption-of-data-in-transit) for all Azure traffic within a region or travelling between regions. With more global regions than any other cloud provider, Azure gives you the flexibility to deploy applications where you need them.
3029

@@ -47,15 +46,17 @@ Microsoft takes a layered approach to physical security, to reduce the risk of u
4746

4847
- **Access request and approval.** You must request access prior to arriving at the datacenter. You're required to provide a valid business justification for your visit, such as compliance or auditing purposes. All requests are approved on a need-to-access basis by Microsoft employees. A need-to-access basis helps keep the number of individuals needed to complete a task in the datacenters to the bare minimum. After Microsoft grants permission, an individual only has access to the discrete area of the datacenter required, based on the approved business justification. Permissions are limited to a certain period of time, and then expire.
4948

50-
- **Facility’s perimeter.** When you arrive at a datacenter, you're required to go through a well-defined access point. Typically, tall fences made of steel and concrete encompass every inch of the perimeter. There are cameras around the datacenters, with a security team monitoring their videos at all times.
49+
- **Visitor access.** Temporary access badges are stored within the access-controlled SOC and inventoried at the beginning and end of each shift. All visitors that have approved access to the datacenter are designated as *Escort Only* on their badges and are required to always remain with their escorts. Escorted visitors do not have any access levels granted to them and can only travel on the access of their escorts. The escort is responsible for reviewing the actions and access of their visitor during their visit to the datacenter. Microsoft requires visitors to surrender badges upon departure from any Microsoft facility. All visitor badges have their access levels removed before they are reused for future visits.
50+
51+
- **Facility's perimeter.** When you arrive at a datacenter, you're required to go through a well-defined access point. Typically, tall fences made of steel and concrete encompass every inch of the perimeter. There are cameras around the datacenters, with a security team monitoring their videos at all times. Security guard patrols ensure entry and exit are restricted to designated areas. Bollards and other measures protect the datacenter exterior from potential threats, including unauthorized access.
5152

5253
- **Building entrance.** The datacenter entrance is staffed with professional security officers who have undergone rigorous training and background checks. These security officers also routinely patrol the datacenter, and monitor the videos of cameras inside the datacenter at all times.
5354

5455
- **Inside the building.** After you enter the building, you must pass two-factor authentication with biometrics to continue moving through the datacenter. If your identity is validated, you can enter only the portion of the datacenter that you have approved access to. You can stay there only for the duration of the time approved.
5556

5657
- **Datacenter floor.** You are only allowed onto the floor that you're approved to enter. You are required to pass a full body metal detection screening. To reduce the risk of unauthorized data entering or leaving the datacenter without our knowledge, only approved devices can make their way into the datacenter floor. Additionally, video cameras monitor the front and back of every server rack. When you exit the datacenter floor, you again must pass through full body metal detection screening. To leave the datacenter, you're required to pass through an additional security scan.
5758

58-
Microsoft requires visitors to surrender badges upon departure from any Microsoft facility.
59+
5960

6061
## Physical security reviews
6162
Periodically, we conduct physical security reviews of the facilities, to ensure the datacenters properly address Azure security requirements. The datacenter hosting provider personnel do not provide Azure service management. Personnel can't sign in to Azure systems and don't have physical access to the Azure collocation room and cages.
@@ -69,7 +70,7 @@ Upon a system's end-of-life, Microsoft operational personnel follow rigorous dat
6970
## Compliance
7071
We design and manage the Azure infrastructure to meet a broad set of international and industry-specific compliance standards, such as ISO 27001, HIPAA, FedRAMP, SOC 1, and SOC 2. We also meet country- or region-specific standards, including Australia IRAP, UK G-Cloud, and Singapore MTCS. Rigorous third-party audits, such as those done by the British Standards Institute, verify adherence to the strict security controls these standards mandate.
7172

72-
For a full list of compliance standards that Azure adheres to, see the [Compliance offerings](https://www.microsoft.com/trustcenter/compliance/complianceofferings).
73+
For a full list of compliance standards that Azure adheres to, see the [Compliance offerings](/azure/compliance/).
7374

7475
## Next steps
7576
To learn more about what Microsoft does to help secure the Azure infrastructure, see:
@@ -83,5 +84,3 @@ To learn more about what Microsoft does to help secure the Azure infrastructure,
8384
- [Azure infrastructure monitoring](infrastructure-monitoring.md)
8485
- [Azure infrastructure integrity](infrastructure-integrity.md)
8586
- [Azure customer data protection](protection-customer-data.md)
86-
87-

0 commit comments

Comments
 (0)