Skip to content

Commit a32418d

Browse files
authored
Merge pull request #79551 from kydeeds/master
Update to JIT Statments
2 parents f3465a0 + b03b179 commit a32418d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-government/documentation-government-plan-security.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,10 +101,10 @@ For Azure operations personnel, the following access principles apply:
101101

102102
* Duties are clearly defined, with separate responsibilities for requesting, approving and deploying changes.
103103
* Access is through defined interfaces that have specific functionality.
104-
* Access is just-in-time (JIT), and is granted only on a per-incident basis or for a specific maintenance event, and always for a limited duration.
104+
* Access is just-in-time (JIT), and is granted on a per-incident basis or for a specific maintenance event, and for a limited duration.
105105
* Access is rule-based, with defined roles that are only assigned the permissions required for troubleshooting.
106106

107-
Screening standards include the validation of US citizenship of all Microsoft support and operational staff before access is granted to Azure Government-hosted systems. Support personnel who need to transfer data use the secure capabilities within Azure Government. Secure data transfer requires a separate set of authentication credentials to gain access. For example, to access system metadata, operations personnel use specific web-based internal management tools, read-only APIs, and JIT elevation.
107+
Screening standards include the validation of US citizenship of all Microsoft support and operational staff before access is granted to Azure Government-hosted systems. Support personnel who need to transfer data use the secure capabilities within Azure Government. Secure data transfer requires a separate set of authentication credentials to gain access.
108108

109109
## Next steps
110110
For supplemental information and updates please subscribe to the

0 commit comments

Comments
 (0)