Security Governance Flashcards
(147 cards)
what are the three major components of the big picture of security architecture beyond cybersecurity? [2.1]
governance, risk, and compliance. governance involves monitoring, auditing, and reporting on security. risk involves identifying, classifying, and mitigating risks (internal, external or unintentional). compliance deals with managing adherence to industry, government, or regulatory requirements
what is azure policy and how does it help in governance? [2.1]
azure policy is a tool for enforcing business rules and assessing compliance with those standards. it allows for the use of both existing microsoft policies and custom policy definitions to ensure compliance with regulatory, cost, or any other required standards. it can also bundle multiple policies into initiatives for large-scale assignment
where can azure policies be applied, and what is recommended for applying them at scale? [2.1]
azure policies can be applied at mgmt groups, subscriptions, resource groups and individual resources. for applying policies at scale, it is recommended to use management groups
what is the relationship between azure policy and azure landing zones? [2.1]
azure policy, when used in conjunction with mgmt groups, is a key building block for azure landing zones, which allow the deployment of secure and scalable azure infrastructure
how does azure policy integrate with ms defender for cloud? [2.1]
azure policy powers large parts of microsoft defender for cloud, enabling security and compliance across cloud resources by enforcing and auditing compliance with security standards
what are the four key times azure policy will be evaluated? [2.1]
- when the policy is first assigned to a scope
- when a resource within the scope is created or updated
- when the policy or initiative itself is updated
- every 24 hours as part of an automatic evaluation cycle
what is the significance of the “effect” property in an azure policy definition? [2.1]
the effect defines what happens when a resource does not meet policy conditions. effects can include deny (blocking changes), append or modify (changing or adding required elements), audit (logging non-compliance), and DeployIfNotExists or Modify (remediation actions)
what is the difference between append and deny effects in azure policy? [2.1]
append allows azure policy to add missing elements, such as required tags, to bring a resource into compliance during deployment. deny blocks the creation or update of a resource if it does not comply disrupting the workflow
what is remediation in azure policy and how is it achieved? [2.1]
remediation is the process of bringing non-compliant resources into compliance. this can be done manually or automatically through remediation tasks, which use a managed identity to authorize and apply changes defined by deployifnotexists or modify effects
how is authorization for remediation tasks provided in azure policy? [2.1]
authorization for remediation tasks is provided through a managed identity that is associated with the policy assignment. this managed identity can have multiple roles as needed to apply the required changes
what is the basic structure of an azure policy definition? [2.1]
- a display name and description
- a mode (all or indexed)
- parameters for reusability across different scenarios
- rules that define conditions for the policy
- effects that define actions when conditions are met
what roles are required for creating and assigning policies in azure? [2.1]
the least privileged role for creating and assigning policies is the resource policy contributor. other roles that can assign policies include security admin and owner
what happens when a policy blocks an action allowed by azure rbac? [2.1]
azure policy takes precendece over azure rbac. if a policy denies an action that azure rbac allows, the action will be blocked by the policy
what is the difference between exclusions and exemptions in azure policy? [2.1]
exclusions remove resources from policy evaluation, making them invisible to compliance results. exemptions allow non-compliant resources to be excluded from enforcement while still appearing in compliance results with recorded reasons for their exemption
what is the purpose of azure blueprints in deploying secure infrastructures? [2.4]
azure blueprints enable cloud architects to define a repeatable set of azure resources that adhere to required standards and security patterns. they package together components like resource groups, policy assignments, role assignments, and ARM templates. these blueprints simplify the deployment process across multiple environments (e.g. separate subscriptions for different clients) by allowing architects to create a blueprint once and deploy it repeatedly. in scenarios where an organization has predefined security requirements or compliance standards, blueprints ensure every deployment follows these guidelines consistently
explain the lifecycle of a blueprint and the role of versioning in azure blueprints? [2.4]
the lifecycle begins with the creation of a blueprint definition. once defined, the blueprint can be saved to a location in the azure management hierarchy (such as management group or subscription). after the blueprint is created and saved, it is published with a version (e.g. version 1) allowing it to be assigned to a target environment. versioning is critical when changes are needed: architects can update the blueprint, publish a new version, and assign the updated blueprint, deploying modified or additional resources as required. this ensures that infrastructure changes are controlled, tracked and consistent across environments. in practice, this would allow iterative improvements to infrastructure without disrupting existing deployments
what are the components (artifacts) that make up an azure blueprint and why are they important? [2.4]
the main artifacts in a blueprint are resource groups, policy assignments, role assignments, and arm templates. these components define the infrastructure, security policies, and access controls that need to be applied.
resource groups: organize resources for a clear structure and management
policy assignments: ensure compliance with security policies (e.g. disabling public blob access)
role assignments: define who has access to what within the deployment
arm templates: allow for detailed and customizable resource deployments (e.g. deploying a storage account)
why is the definition location of a blueprint important, and what impact does it have on deployments? [2.4]
the definition location determines where the blueprint is stored and, more importantly, where it can be deployed. for example, if a blueprint is saved to a management group above multiple subscriptions, it can be deployed across those subscriptions. this is particularly useful for organizations managing multiple environments under different subscriptions, such as global businesses with region-specific deployments. by saving a blueprint at a higher level in the management hierarchy, architects ensure they can deploy that blueprint consistently across multiple subscriptions without duplicating effort
what is the role of a managed identity in deploying a blueprint, and why is it essential? [2.4]
a managed identity is required for deploying the resources defined in a blueprint. the managed identity needs to have the necessary privileges to create or modify those resources. when a blueprint is assigned, it uses this identity to execute the deployment process securely. without an appropriate managed identity, the blueprint would not have the necessary permissions to carry out tasks like creating a storage account or enforcing policy assignments, which could cause deployment failures. in scenarios like multi-client environments, ensuring the correct privileges are assigned is key to maintaining secure and compliant deployments
what is a lock in azure blueprints, and how does it differ from resource locks? [2.4]
when assigning a blueprint, you can apply a lock that creates an azure role-based access control deny assignment. this lock restricts changes to the deployed resources, even if a user has administrative permissions. this is different from a standard resource lock, which prevents users from modifying or deleting individual resources. in contrast, a blueprint lock denies all changes, preventing the modification of the entire deployment structure. this feature is particularly valuable when managing environments where strict governance is required, such as in finance or healthcare, where unauthorized changes to infrastructure could lead to compliance violations
how does versioning and assignment of blueprints allow for flexibility in managing azure resources? [2.4]
versioning in blueprints allows for the controlled evolution of infrastructure. if updates or changes are needed, a new version of the blueprint can be created and assigned, ensuring that updates to resources are rolled out in a managed, traceable manner.
what is microsoft defender for cloud used for? [2.5]
service used to secure cloud-based applications and data. it provides protection throughout a workload’s lifecycle, from pre-deployment to post-deployment.
what are the stages of a workload lifecycle in azure? [2.5]
the lifecycle includes pre-deployment (as code or software), deployment (to azure, on-prem, or other clouds), and post-deployment, where users generate and store data
what does infrastructure as code (IaC) refer to in cloud deployment? [2.5]
iac is code that represents infrastructure (e.g. virtual machines, networks) or the code that powers application functions, allowing infrastructure to be managed and provisioned through software