Policy templates
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 policy template).
These pages document release v1.5.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
| Kind | What it is |
|---|---|
| Hardening | A set of security checks on one topic, such as management access, AAA, SNMP, logging or services. Assign it as it is, or remove the rules that do not apply to your network. |
| Operational standards | Checks for drift from your own operational standard (NTP, syslog and DNS servers, login banner, interface descriptions, hostname pattern, SNMP location), or a baseline standard with one block per section (Cisco ios-baseline). It is a template to edit: the rules use RFC 5737 and other example values, so expect them to fail until you replace those values with your own. |
| Build template | A starting template for a new device build, with example values (hostnames, addresses, servers) to replace with your own. It is not a compliance check: expect its rules to fail until you replace the example values. |
| Framework | A generated file that collects, from the hardening files, every rule that lists a reference for one framework (NIST SP 800-53, NIST CSF 1.1, HIPAA or ISO/IEC 27001:2022). Every vendor with hardening files has them except F5 BIG-IP, whose rules list no references. |
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 (see the Juniper page), and the Palo Alto files for the brace format of show config running (see the Palo Alto page).
A file needs the highest minimum version of any method it contains. See minimum versions.
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.