Stock policy definitions

Stock policy definitions

rConfig publishes a set of ready-made policy definition files in the rconfig/pro-policy-definitions repository on GitHub. They are organised by vendor, and you load them into rConfig with Import Templates (see importing a stock template).

These pages document release v1.4.0. Each vendor page lists every rule in each topic file, the method it uses and what it checks, and the framework files built from them.

Kinds of file

Topic files and framework files

The hardening files are topic files: each holds the rules for one topic, and each rule appears in exactly one topic file. A framework file holds no rules of its own: it copies, unchanged, the hardening rules that reference one framework, so you can assign the same checks by topic or by framework and each rule gives the same result either way. A framework file lists checks relevant to that framework; it is not a certification or a full assessment.

Vendors and files

The Juniper files are written for display set format and have not yet been checked against a real Junos device (see the Juniper page).

A file needs the highest minimum version of any method it contains. See minimum versions.

Status labels

Each file’s .meta.yaml sidecar records a status:

The status says how a file was tested, not that its rules pass on any particular device. It is separate from the Lab tested and Verified statuses on the platform pages, which mean an automated rConfig Pro test asserts the result shown.

References

Hardening files can list published references for each rule in their sidecar: a NIST SP 800-53 control, a HIPAA 45 CFR section, a NIST CSF 1.1 subcategory or an ISO/IEC 27001:2022 Annex A control. The vendor pages show them where a rule has one. They record controls the rule is relevant to, and the framework files are built from them. A rule provides evidence towards a control; it does not make a device compliant with it.