Audit-log coverage reporting
that stays on your network

Auditors ask whether you log access, changes to accounts and permissions, and attempts to clear logs. Arden Comply reads your existing Windows event logs and shows, requirement by requirement, which of that logging is in place and where the gaps are. It runs on your own server, and nothing is sent to the cloud. It documents your logging; it does not decide whether you are compliant.

Request a Beta Invite See Mapped Controls

Runs on your own server, with no cloud service involved

FedRAMP authorization is for cloud services that process federal data on a provider's infrastructure. Arden isn't a cloud service. It runs on your own server, and the agents send logs only to that server, so there is no third-party system holding your data for an assessor to review. Arden itself still sits inside your environment and goes through the same review you apply to any other on-premises software.

GovRAMP

GovRAMP (formerly StateRAMP) assesses cloud products sold to state and local governments. Arden has no cloud component, so there is no hosted service for GovRAMP to assess. Your agency would evaluate it the way it evaluates other software installed on its own systems.

Cryptography, stated plainly

Credentials Arden stores (endpoint deployment and SMTP passwords) are encrypted with Windows DPAPI. Dashboard TLS uses the OpenSSL library bundled with Arden, and the agent uses Go’s standard TLS. Arden does not currently run in a FIPS 140-3 validated mode. If your policy requires FIPS-validated cryptography, contact us before deploying.

Why running on-premises helps
Your event logs stay on a server you control. For this tool, there's no vendor cloud whose controls you need to assess and no third party receiving your log data. When an assessor asks where the logs are stored, the answer is your Arden server.

Requirements mapped to Windows event logs

Arden maps 133 requirements across seven frameworks to 56 Windows event categories. Windows logs 19 of those categories by default. The rest depend on audit policy, and the report lists the Group Policy settings that turn them on. In the dashboard you can pick frameworks, open individual requirements, and export the results grouped by control.
What this report can and can't tell you. Arden Comply shows which event categories each requirement depends on and whether those events were observed in your logs. It does not decide whether you are compliant, and it doesn't replace your auditor or assessor. That decision is theirs, and many requirements involve policies, training, or physical safeguards that event logs can't show.

CJIS Security Policy v6.0

Criminal Justice Information Services

Agencies that handle criminal justice information have to log and review access to CJI systems. The CJIS policy also puts encryption and access-control conditions on cloud services. Arden runs on your own server, and the logs it collects stay on your network.

✓ 15 requirements mapped — NIST SP 800-53 Rev. 5 control IDs, as used by CJIS v6.0: AU-2 Event Logging, AU-3 Content of Audit Records, AU-6 Audit Review & Reporting, AU-9 Protection of Audit Information
✓ Access Control (AC) — AC-2 Account Management, AC-3 Access Enforcement, AC-6 Least Privilege, AC-7 Unsuccessful Logons, AC-11 Device Lock, AC-12 Session Termination, AC-17 Remote Access
✓ Identification & Authentication (IA) — IA-2(1)/(2) Multi-Factor Authentication, IA-4 Identifier Management, IA-5 Authenticator Management
✓ Logon & account events — Computer account changes, universal group membership changes, and logon/logoff events

HIPAA

Health Insurance Portability & Accountability Act

The HIPAA Security Rule calls for audit controls that record and examine activity on systems containing ePHI. A small clinic has the same requirement as a hospital system, often without a SIEM or anyone on staff to run one.

✓ 14 requirements mapped — §164.312(b) Audit Controls, §164.312(a)(1) Access Control, §164.312(a)(2)(i) Unique User ID, §164.312(a)(2)(iii) Auto Logoff, §164.312(d) Authentication
✓ §164.308(a) Admin Safeguards — Security Management Process, Activity Review, Workforce Security, Information Access Management, Log-in Monitoring, Password Management, Incident Procedures
✓ §164.312 Technical Safeguards — Integrity Controls and Transmission Security, mapped to computer account and group membership events
✓ Exports by control — CSV and JSON exports grouped by HIPAA control, which you can filter by category, username, or computer

PCI DSS v4.0.1

Payment Card Industry Data Security Standard

PCI DSS requires any business that stores, processes, or transmits cardholder data to log and monitor access to system components and cardholder data. That includes restaurants and shops running Windows-based point-of-sale systems.

✓ 15 requirements mapped — Req 1.2 Network Security Controls, 2.2 Secure Configuration, 6.3.3 Patching, 6.5 Change Management, 7.2–7.3 Access Control, 8.2, 8.3 & 8.6 Identification, Authentication & System Accounts
✓ Req 10 Logging & Monitoring — 10.2 Audit Logs, 10.3 Log Protection, 10.4 Log Review, 10.5 Log Retention, 10.6 Time Synchronization, 10.7 Critical Control Failures
✓ Computer accounts — Machine account events are mapped alongside user account events
✓ Group membership — Membership changes to local, global, and universal groups

CMMC 2.0 / NIST SP 800-171

Cybersecurity Maturity Model Certification

CMMC Level 2 assessments are based on the NIST SP 800-171 requirements, including the audit and accountability family. Many of the contractors and subcontractors going through them are small shops without a security team or a SIEM.

✓ 35 CMMC practices & 31 NIST SP 800-171 Rev. 3 requirements mapped — The largest set in the report, spread across AC, AU, CM, IA, IR, SC, and SI
✓ Access Control (AC.L1/L2-3.1.x) — System access limits, least privilege, privileged functions, unsuccessful logon attempts, remote access, CUI flow control
✓ Audit & Accountability (AU.L2-3.3.x) — Audit log creation & retention, user traceability, logged-event review, logging-failure alerts, correlation, reporting, and protection
✓ IA, CM, IR & SI — User & device identification, configuration baselines and change tracking, incident handling, and system monitoring for attacks

SOX

Sarbanes-Oxley Act

For public companies, SOX auditors test IT general controls over financial reporting systems, including who has access and how changes are made. Windows logon, account, and change events are part of what they look at.

✓ 12 ITGC areas mapped — Logical access to programs & data, IT general controls over financial reporting (§302/§404), financial system access, user lifecycle
✓ Access & Privilege Monitoring — Privileged access, segregation of duties, universal group membership changes, and remote session tracking
✓ Change Management — Service installations, scheduled task lifecycle (created, enabled, updated, deleted), and audit policy changes
✓ Log integrity — Log clearing detection, audit trail protection, and computer account changes

FERPA

Family Educational Rights & Privacy Act

Schools, districts, and colleges are responsible for protecting student education records. Their IT staff look after Windows labs and student information systems, usually without a dedicated security person.

✓ 11 areas mapped — Access Monitoring, Unauthorized Access Detection, Account Management, Privilege Management, Education Record Access, Remote Access
✓ Session & System Changes — Session termination tracking, service installations, scheduled task lifecycle, and audit policy changes
✓ Log integrity — Log clearing detection, audit trail protection, and computer account changes
✓ Pricing — Not announced yet. The plan is a flat monthly rate based on environment size, with no per-GB ingest fees

What the report shows an auditor

Auditors usually want to see that the relevant events are being logged, that someone reviews them, and that the logs are kept. Arden's report covers the first part in detail and gives you exports to support the rest.

Stays on your network

Agents send logs only to your Arden server, which does the analysis and storage. Nothing is sent to a cloud service, and there is no telemetry.

Emergency Log Preservation

When Arden sees a log-clearing event, it writes the alerts and events it has already collected to a local preservation file, so you still have a copy after the endpoint's log has been wiped.

User Attribution

For account changes, privilege assignments, and policy changes, Arden records which user account made the change, as reported in the Windows event.

Continuous Audit Log

Events in the 56 monitored categories, including logons, user and computer account changes, privilege use, group membership, scheduled tasks, and policy changes, are written to a rolling CSV file as they arrive. You can export them as CSV or JSON, filtered by framework and control.

PDF coverage reports

You can generate a PDF audit-log coverage report from the dashboard. It shows coverage by framework, which baseline and enriched event categories were observed for each requirement, the logging gaps, an endpoint inventory, and recommended audit-policy changes. You can give it to your auditor or assessor as documentation of your logging.

Audit Policy Gap Analysis

For each requirement, Arden shows which event categories were observed, which probably need an audit-policy change, and which may be limited by the Windows edition or version. Each gap comes with a suggested Group Policy setting, or a note when the limit is in the OS itself.

Updates as your logging changes

After you enable an audit policy and those events start arriving, the dashboard picks them up and marks that category as observed. You don't need to reconfigure Arden or run a new scan.

Beta

Request a beta invite

The beta is invite-only, with two-week licenses. Arden Comply runs on Windows 10/11 or Server 2016 and later as a single executable, with no database or runtime to install.

Request a Beta Invite →
Arden Complete adds threat detection. See Arden Complete →