AzPolicyAdvertizer

last sync: 2025-Apr-29 17:16:02 UTC

Microsoft Managed Control 1089 - Security Awareness | Regulatory Compliance - Awareness and Training

Azure BuiltIn Policy definition

Source Azure Portal
Display name Microsoft Managed Control 1089 - Security Awareness
Id ef080e67-0d1a-4f76-a0c5-fb9b0358485e
Version 1.0.1
Details on versioning
Versioning Versions supported for Versioning: 0
Built-in Versioning [Preview]
Category Regulatory Compliance
Microsoft Learn
Description Microsoft implements this Awareness and Training control
Cloud environments AzureCloud = true
AzureUSGovernment = true
AzureChinaCloud = unknown
Available in AzUSGov The Policy is available in AzureUSGovernment cloud. Version: '1.0.0'
Repository: Azure-Policy ef080e67-0d1a-4f76-a0c5-fb9b0358485e
Additional metadata Name/Id: ACF1089 / Microsoft Managed Control 1089
Category: Awareness and Training
Title: Security Awareness Training - New User Training
Ownership: Customer, Microsoft
Description: The organization provides basic security awareness training to information system users (including managers, senior executives, and contractors): As part of initial training for new users;
Requirements: The annual security foundations training includes basic level training on how to detect, report and implement best practices to safeguard Microsoft and its customers. This course also covers the security requirements and expectations for elevated privileges in production environments. Engineering personnel participate in ongoing role-based security training through the STRIKE program. STRIKE provides regular 200-400 level sessions, labs, online courses, and material to engage, educate, and empower engineers to securely design and operate services. Azure requires all personnel to complete the following training as part of their onboarding process: * Security Foundations course – Azure new hire personnel are required to take the Security Foundations course within thirty (30) days of employment, and annually thereafter for non-engineering personnel. * STRIKE – Azure engineering personnel are required to participate in STRIKE annually. Participation includes in-person events, sessions, labs, and online courses.
Mode Indexed
Type Static
Preview False
Deprecated False
Effect Fixed
audit
RBAC role(s) none
Rule aliases none
Rule resource types IF (2)
Compliance
The following 1 compliance controls are associated with this Policy definition 'Microsoft Managed Control 1089 - Security Awareness' (ef080e67-0d1a-4f76-a0c5-fb9b0358485e)
Control Domain Control Name MetadataId Category Title Owner Requirements Description Info Policy#
NIS2 Cybersecurity_training_7 NIS2_Cybersecurity_training_7 NIS2_Cybersecurity_training_7 Cybersecurity training Basic cybersecurity hygiene and training Customer, Microsoft Security Training Records - Documentation Essential and important entities should adopt a wide range of basic cyber hygiene practices, such as zero-trust principles, software updates, device configuration, network segmentation, identity and access management or user awareness, organise training for their staff and raise awareness concerning cyber threats, phishing or social engineering techniques. Cyber hygiene policies provide the foundations for protecting network and information system infrastructures, hardware, software and online application security, and business or end-user data upon which entities rely. Cyber hygiene policies comprising a common baseline set of practices, including software and hardware updates, password changes, the management of new installs, the limitation of administrator-level access accounts, and the backing-up of data, enable a proactive framework of preparedness and overall safety and security in the event of incidents or cyber threats. ENISA should monitor and analyse Member States’ cyber hygiene policies. 8
Initiatives usage
Initiative DisplayName Initiative Id Initiative Category State Type polSet in AzUSGov
[Preview]: NIS2 32ff9e30-4725-4ca7-ba3a-904a7721ee87 Regulatory Compliance Preview BuiltIn unknown
History
Date/Time (UTC ymd) (i) Change type Change detail
2022-04-01 20:29:14 change Patch (1.0.0 > 1.0.1)
JSON compare
compare mode: version left: version right:
JSON
api-version=2021-06-01
EPAC