Primary references
Use the original standards below to check terminology and requirements. These references explain the standards; they do not endorse CISGuard or independently verify its product coverage.
All answers
How long does CISGuard deployment take?
Onboarding is managed: our compliance engineers deploy the server, configure benchmarks and schedules, integrate identity, and train your team, so deployment is seamless from the first day. Air-gapped deployments add a media-transfer step; the long path is usually customer-side change approval rather than installation. Your first scan runs as soon as agents register, and framework evidence builds from the first scheduled cycle.
The longer answer.
The server runs on Windows Server 2019 or later, or on Linux (RHEL 8 or later, Ubuntu 20.04 or later), with 8 GB of RAM and 100 GB of disk. Agents install on Windows and Linux endpoints, while Azure, AWS and Microsoft 365 are connected through their native APIs without agents.
Because CISGuard compliance engineers run the onboarding, your team does not have to learn the installer. Most of the elapsed time sits in your own change process: approving the server, opening the paths agents use to report in, and, for air-gapped sites, moving signed media across the boundary.
More questions on CISGuard?
Our compliance engineers can show you exactly how CISGuard handles CISGuard in a briefing scoped to your environment.