Rediger

Use Azure Policy to secure your Nexus resources

  • Artikel

In this article, you'll learn how to use Azure Policy to secure and validate the compliance status of your Nexus resources.

Before you begin

If you're new to Azure Policy, here are some helpful resources that you can use to become more familiar with Azure Policy.

Understanding Policy Definitions and Assignments
  • Policy Definitions: These are the rules that your resources need to comply with. They can be built-in or custom.
  • Assignments: The process of applying a policy definition to your resources.
Steps for security enforcement
  1. Explore built-in policies: Review built-in policies relevant to Nexus Bare Metal Machine (BMM) resources.
  2. Customize policies: Customize policies to address specific needs of your resources.
  3. Policy assignment: Assign policies through the Azure portal, ensuring correct scope.
  4. Monitoring and compliance: Regularly monitor policy compliance using Azure tools.
  5. Troubleshooting: Address common issues that arise during policy assignment.
Visual Guides and Examples

Prerequisites

  • One or more on-premises Nexus resources that are Arc-connected to Azure.

    Note

    Operator Nexus does not require you to install the Azure Policy add-on for the Undercloud Kubernetes connected cluster or BMM connected machine resources since the extensions are automatically installed during cluster deployment.

  • A user account in your subscription with the appropriate role:

    • A Resource Policy Contributor or Owner can view, create, assign, and disable policies.
    • A Contributor or Reader can view policies and policy assignments.

    Preparation Checklist:

    • Familiarize with Azure CLI or PowerShell for policy management.
    • Review your organization's security and compliance requirements.
    • Identify specific Azure Policy features relevant to your needs.

Use Azure Policy to secure your Nexus BMM resources

The Operator Nexus service offers a built-in policy definition that is recommended to be assigned to your Nexus BMM resources. This policy definition is called [Preview]: Nexus compute machines should meet security baseline. This policy definition is used to ensure that your Nexus BMM resources are configured with industry best practice security settings.

Use Azure Policy to secure your Nexus Kubernetes cluster

Operator Nexus Arc-connected Nexus Kubernetes do not yet have built-in policy definitions available. However, you can create custom policy definitions to meet your organization's security and compliance requirements or utilize built-in policy definitions for AKS clusters.

Customizing Policies for Nexus Kubernetes cluster

  • Customize policies considering the unique aspects of Nexus Kubernetes clusters, such as network configurations and container security.
  • Refer to Custom policy definitions for guidance.

Apply and validate Policies for Nexus resources

Whether you are securing Nexus BMM resources or Nexus Kubernetes clusters, the process of applying and validating policies is similar. Here's a generalized approach:

  1. Identify Suitable Policies:

  2. Assign Policies:

    • Utilize the Azure portal to assign these policies to your Nexus resources.
    • Ensure the correct scope of assignment, which could be at the subscription, resource group, or individual resource level.
    • For custom policies, follow the guidelines in Creating custom policy definitions.

  3. Validate Policy Application:

    • Post assignment, validate that the policies are correctly applied and are effectively monitoring compliance.
    • Utilize Azure compliance tools and dashboards for ongoing monitoring and reporting.
    • For detailed steps on validation, refer to Validating Azure Policy.

This approach ensures that all your Operator Nexus resources, regardless of their type, are secured and compliant with your organizational policies, utilizing the powerful capabilities of Azure Policy.