Introduction

Sicura Agent is an auxiliary tool used with the Sicura Console to provide compliance scans and enforce compliance on a node.

System Requirements

Sicura Agent has full scanning and enforcement support for various versions of Windows as well as numerous Linux distributions.

Windows:

Scanners included: jScat, CIS-CAT Assessor Pro v4
Bolt enforcement supported: true
Versions supported: Windows Server 2012 R2, Windows Server 2016, Windows Server 2019

Linux

Scanners included: OpenSCAP, CIS-CAT Assessor Pro v4, ~~Compliance Engine~~ DEPRECATED
Bolt enforcement supported: true
Versions supported:
- RHEL: 7,8
- Oracle Linux: 7,8
- CentOS: 7,8

The Agent uses minimal system resources until the time of scanning/enforcement. Expect the normal load usually used by whatever ability type is being run.

We recommend running the agent on a system with:

1gb of free HDD space
2gb RAM minimum, 6gb recommended
quad-core CPU

Getting Started

The only step required to get up and running is to connect the Sicura Agent to your Sicura Console instance.

This is done by ensuring a DNS entry is made matching sicura-console-collector to the valid IP or hostname of your Console instance. If this cannot be done due to restrictive policy or you’d like to override the default, the IP or hostname can be entered to the collector .

Furthermore, ensure the collector-port and collector-https configuration options are set properly to match console configuration.

Once initial configuration is complete, the agent can be started with sicura-agent or systemctl start sicura-agent commands (On all Windows machines, the Sicura Agent service is started by default).