---
title: "Policy library"
description: "Ready-made policies you can apply as they are or adapt."
product: "Guardian"
edition: "Classic"
type: "reference"
url: "https://docs.cloudhouse.com/guardian/classic/control/policies/policy-library/"
---
# Policy library

Ready-made policies you can apply as they are or adapt. For example, you could create a policy to ensure that a set of roles and features are installed on a node, or that certain environment variables are set. The policy checks are then run each time the node is scanned, with the results indicating whether the checks passed or failed. A node group can contain multiple policies that are applied to the same or a different set of nodes. For more information on how to import a policy into Guardian, see [Import a Policy](https://docs.cloudhouse.com/guardian/classic/control/policies/export-import-policy/index.md#import-a-policy).

Applies to: `Guardian Classic`

!!! tip

    Additionally, you can access our [public repository of policies](https://github.com/cloudhousetech/content/tree/master/policies).

## AWS IAM password and permissions

**Node Type**: AWS IAM Account

**Download Link**: [AWS IAM Best Practice](https://github.com/cloudhousetech/content/blob/master/policies/aws_iam_best_practice.json)

**Description**: This policy confirms the following:

- Certain recommended password policy settings.
- No issued user access keys have been left unused for more than six months.
- Users have Multi-Factor Authentication (**MFA**) enabled.
- Users only have one MFA device configured.
- Users have no inline or managed policies assigned to them, as per RBAC's recommendation.

## BlueKeep (CVE-2019-0708) check

**Node Type**: Windows

**Download Link**: [BlueKeep Check](https://github.com/cloudhousetech/content/blob/master/policies/bluekeep-cve-check-policy.json)

**Description**: This policy checks that the node is not vulnerable to the BlueKeep vuln.

## GitHub user identity check

**Node Type**: GitHub Organisation

**Download Link**: [GitHub User Identity Check](https://github.com/cloudhousetech/content/blob/master/policies/githubUserFullNamePolicy.json)

**Description**: This policy confirms that all users in your GitHub account have the full name attribute set in their user profiles so you can audit who did what when relative to a real person's identity.

## GitHub users MFA check

**Node Type**: GitHub Organisation

**Download Link**: [GitHub Users MFA Check](https://github.com/cloudhousetech/content/blob/master/policies/github2FApolicy.json)

**Description**: This policy confirms that all users in your GitHub account have MFA enabled.

## GitHub repository is not forked

**Node Type**: GitHub Organisation

**Download Link**: [GitHub Repo is not Forked](https://github.com/cloudhousetech/content/blob/master/policies/githubRepoIsNotFork.json)

**Description**: This policy checks that your GitHub Repo has not been forked and is not a fork itself.

## GitHub repository is private

**Node Type**: GitHub Organisation

**Download Link**: [GitHub Repo Private](https://github.com/cloudhousetech/content/blob/master/policies/githubPrivateRepoPolicy.json)

**Description**: This policy checks that your GitHub Repo is private and not public.

## PCI section 3.2 – Windows audit check

**Node Type**: Windows

**Download Link**: [PCI Section 3.2 – Audit Check Windows](https://github.com/cloudhousetech/content/blob/master/policies/PCI_3_2_Audit_Check_Windows.json)

**Description**: This policy checks to validate password complexity and server hardening requirements for PCI compliance.

## PCI section 3.2 – MS-SQL Windows

**Node Type**: MS-SQL

**Download Link**: [PCI Section 3.2 – MS-SQL Windows](https://github.com/cloudhousetech/content/blob/master/policies/PCI_3_2_MS-SQL_Windows.json)

**Description**: This policy checks to validate password complexity and server hardening requirements for PCI compliance.

## PCI section 3.2 – Password complexity RHEL7

**Node Type**: RHEL7

**Download Link**: [PCI Section 3.2 – Password Check RHEL7](https://github.com/cloudhousetech/content/blob/master/policies/PCI_3_2_Password_Check_RHEL7.json)

**Description**: This policy checks to validate password complexity and server hardening requirements for PCI compliance.

## PCI section 3.2 – Password complexity Windows

**Node Type**: Windows

**Download Link**: [PCI Section 3.2 – Password Check Windows](https://github.com/cloudhousetech/content/blob/master/policies/PCI_3_2_Password_Check_Windows.json)

**Description**: This policy checks to validate password complexity and server hardening requirements for PCI compliance.

## PCI section 3.2 – Server hardening Windows

**Node Type**: Windows

**Download Link**: [PCI Section 3.2 – Server Hardening Windows](https://github.com/cloudhousetech/content/blob/master/policies/PCI_3_2_Server_Hardening_Windows.json)

**Description**: This policy checks to validate password complexity and server hardening requirements for PCI compliance.

## Website CyberRisk checks

**Node Type**: Windows

**Download Link**: [CyberRisk](https://github.com/cloudhousetech/content/blob/master/policies/CyberRisk.json)

**Description**: This policy provides a basic set of checks your internal and external websites should adhere to and is inspired by the checks used in UpGuard CyberRisk.