TroutTrout

Your first three weeks

Simple

After the quick start: protect your machines on day 1, add users, sign-in and vendor access in week 1, then logs, SIEM and a compliance report.

3 min read · Last updated 2026-10-17

On day 1 you follow the quick start and your machines are behind Access Gate. In week 1 you add people: users, sign-in before anyone reaches a machine, and remote access for your vendors. In week 2 you collect the evidence: logs, your SIEM, and a risk and compliance report.

WhenGoalWhat you do
Day 1Your machines are protectedThe four quick-start steps
Week 1The right people reach the right machinesUsers, sign-in, vendor remote access
Week 2You can prove itLogs, SIEM, risk and compliance report

Day 1: protect your machines

Follow the quick start. It takes about an hour:

  1. Map your network from a short capture in the network analyzer.
  2. Create your inventory and enclaves: name your machines and decide who reaches them. See Build your asset inventory and Protect a machine with an enclave.
  3. Connect Access Gate beside your router with two cables.
  4. Switch with one rule on your router.

Access Gate keeps watching your network after that, so new machines show up on their own. To feed it a copy of the traffic from your router, see Configure the monitoring port.

Week 1: add people

  1. Add your users. Create them in Access Gate, or sync them from your directory. See Manage users with the Access Gate directory.
  2. Decide who reaches what. Allow each user or group only the machines and protocols they need. See Access control lists.
  3. Make people sign in before they reach a machine. See Authenticate users with access screens.
  4. Give vendors remote access to one machine, for the time of the job, with the session recorded. See Remote zero trust access and Privileged access management. The example vendor intervention process walks through a full job.
  5. Turn on alerts for unusual activity. See Detection and alerts.

Week 2: collect the evidence

  1. Find your logs on Access Gate. See System logs and diagnostics.
  2. Send them to your SIEM. See Log forwarding and SIEM export.
  3. Run a risk assessment and export the compliance report. See Create and export a risk assessment report.

Where you are after three weeks

You haveCMMC controls it supports
A complete list of your machinesCM.L2-3.4.1
Sign-in and per-person access to each machineAC.L2-3.1.1, AC.L2-3.1.2
Your machines separated into enclavesSC.L2-3.13.1
Encrypted connectionsSC.L2-3.13.11
Logs of who reached whatAU.L2-3.3.1 to AU.L2-3.3.9
What you need to respond to an incidentIR.L2-3.6.1