Home > Storage > PowerScale (Isilon) > Product Documentation > Security and Compliance > Dell PowerScale OneFS: Security Considerations > Process
OneFS runs through a battery of steps when the security profile is applied. These steps remain in the background and are not displayed throughout the process. This section examines a subset of the OneFS process that follows initiation of the hardening command.
The security profile is applied through the CLI and API. After the hardening command is run, the hardening engine is launched, and the engine applies the security profile. The hardening engine is also responsible for hardening new nodes as they are added to a cluster.
For OneFS 9.4.0.0 and earlier, the node hardening state information is stored in /etc/ifs/hardening_info.txt. It contains the date, OneFS build, policy file path, and the cluster hostname, as shown in the following figure.
For OneFS 9.5.0.0 and later, you can find the cluster hardening state information by running the isi hardening reports create command followed by the isi hardening reports list command. The Applied field displays either Yes or No, and the Status field displays either Compliant or Not Compliant.
Further, after you create a hardening report, you can run the isi hardening reports view STIG command to list the status of all STIG configuration parameters. Using the --verbose option, you can obtain verbose output.