PCI DSS · Global

PCI DSS Requirement 10, with the logs in your own environment.

What PCI DSS v4.0.1 asks of your logs: the events to capture, protecting them, automated daily review, a year of history with three months ready to search, synchronized clocks, and alerts when logging fails. nano is a SIEM you run inside your own environment, and your logs never reach nano.

Buy nano
Talk to sales
Requirement 10, line by line

What Requirement 10 asks of your logs.

Each line: the requirement in brief, what it means in practice, and where nano fits. Requirement numbers follow PCI DSS v4.0.1.

PCI DSS v4.0.1, Requirement 10: Log and monitor all access to system components and cardholder data

Applies to the system components in or connected to your cardholder data environment (CDE). Requirements are summarized; the standard has the full wording and testing procedures.

Ref The requirement, in brief In plain English How nano helps
10.2.1 Audit logs are enabled and active for all system components and cardholder data. PCI SSC · PCI DSS v4.0.1 Every in-scope system logs, and the logs actually arrive somewhere you can use them.
Collects logs from the sources you onboard from the catalog over HEC, HTTP, OTLP, cloud pull or Vector agents, into one store in your environment. Every install starts with zero log sources, so your onboarding list is your in-scope inventory.
10.2.1.1 to 10.2.1.7 Logs capture individual user access to cardholder data, all actions by administrators, access to audit logs, invalid access attempts, changes to identification and authentication credentials, starting, stopping or pausing of audit logs, and creation or deletion of system-level objects. PCI SSC · PCI DSS v4.0.1 Seven event types every in-scope system must record. The SIEM is where you check they are all there.
Detections over normalized OCSF events can watch for each type, for example an audit log being cleared or a new admin account. nano's own audit log records sign-ins, user and role changes and every Audit Log export, so access to the SIEM is logged too.
10.2.2 Each log entry records user identification, type of event, date and time, success or failure, origination of the event, and the identity of the affected data, component or resource. PCI SSC · PCI DSS v4.0.1 Six details per event, so an investigator can tell who did what, when, from where and to what.
Events are normalized to OCSF at ingest, so user, activity, time, status, source endpoint and target land in the same fields whatever the source.
10.3.1 to 10.3.4 Read access to audit logs is limited to those with a job-related need; logs are protected from modification; logs are promptly backed up to a secure, central, internal log server or media that is difficult to modify; file integrity monitoring or change detection is used on audit logs. PCI SSC · PCI DSS v4.0.1 Lock the logs down, get copies off the source quickly, and know if anyone changes them.
nano is the central, internal log server, on infrastructure you control. Roles and source visibility limit who can read which logs; retention changes go to the platform audit log. Run your file integrity monitoring on the log store hosts as you would on any other in-scope system.
10.4.1 · 10.4.1.1 Security events and the logs of CDE components, critical systems and security functions are reviewed at least once daily (10.4.1). Automated mechanisms perform those audit log reviews (10.4.1.1). PCI SSC · PCI DSS v4.0.1 Daily review, and since 31 March 2025 it has to be automated. Manual review alone no longer meets it.
Detection rules run on events as they arrive and raise alerts. Risk-based alerting rolls related weak signals into one alert, so a daily review starts from a short queue, not raw logs.
10.4.2 · 10.4.2.1 · 10.4.3 Logs of other system components are reviewed periodically, at a frequency set by your targeted risk analysis; exceptions and anomalies found in review are addressed. PCI SSC · PCI DSS v4.0.1 Lower-risk systems can be reviewed less often, if your risk analysis says so. Whatever you find, you follow up.
The same detections cover lower-risk sources; alerts group into cases, which record the follow-up, who did it and when.
10.5.1 Audit log history is retained for at least 12 months, with at least the most recent three months immediately available for analysis. PCI SSC · PCI DSS v4.0.1 A year in total. The last three months must be searchable right away, not waiting on a restore.
Event retention is a setting, 365 days by default. Set it to at least 366 days, or 13 months, so the previous 12 calendar months are always covered. Recent data stays on fast disk and older data can tier to your own S3-compatible storage, where it stays searchable without a restore.
10.6.1 to 10.6.3 System clocks are synchronized with time-synchronization technology, configured to correct and consistent time from designated time servers, and time settings and data are protected. PCI SSC · PCI DSS v4.0.1 Every clock agrees, so events from different systems line up in an investigation.
Clock sync is a host setting: because you run the servers, you point nano's hosts and your sources at your designated time servers. nano refuses a license check-in from a host more than five minutes off real time, which flags a drifting clock.
10.7.1 · 10.7.2 · 10.7.3 Failures of critical security control systems, including audit logging mechanisms and automated log review, are detected, alerted and addressed promptly, and responded to. PCI SSC · PCI DSS v4.0.1 If logging or log review stops, you must find out quickly and fix it. Since 31 March 2025 this applies to every entity, not only service providers.
nano's optional monitoring stack alerts when ingest stalls or drops events and can send those alerts into nano. A search of the latest event time by source shows which sources have gone quiet.
Versions and dates

Every v4.x requirement is now in force.

The future-dated requirements, including the logging ones, stopped being best practice on 31 March 2025.

  1. 31 Mar 2024 In effect

    v3.2.1 retired

    PCI DSS v4.x becomes the only active version of the standard.

    PCI SSC blog · future-dated ↗
  2. Jun 2024 In effect

    v4.0.1 published

    A limited revision of v4.0, with clarifications. It does not move the future-dated deadline.

    PCI SSC blog · future-dated ↗
  3. 31 Mar 2025 In effect

    Future-dated requirements

    The 51 requirements that were best practice become mandatory, including automated log review (10.4.1.1) and control-failure detection for all entities (10.7.2).

    PCI SSC blog · future-dated ↗
nano and your assessment

Software you run, assessed as part of your environment.

A SIEM that holds your CDE's logs matters to your assessment either way. What changes when you run it yourself is who else holds the logs.

Not a log-holding provider

Your logs stay in your environment

nano, LLC, the vendor, never receives your logs and has no standing access to your install, so it is not another provider holding your CDE's audit trail. The nano software you run stores and processes whatever your sources send it.

In your assessment

The SIEM you run is assessed with you

If any source sends nano account data, such as a log line with a full card number, your nano install stores it and sits in your CDE scope. Mask or drop PAN at the source to keep it out, and confirm scope with your QSA. Either way, the SIEM runs under your own controls, segmentation and evidence.

Your responsibility

Requirement 10 is still yours

nano supplies the logging, alerting, retention and search. Your policies, daily review process, time servers and responses are what the assessor tests.

Inside your environment

A central log server, on infrastructure you control.

nano installs with Docker Compose or with Helm on Kubernetes, on your servers or in your own cloud account. Sources send logs to it over your network, and it parses, stores, searches and runs detections on them there.

Your environment

Your data center, your own AWS, Azure or Google Cloud account, or an air-gapped network

01 · Sources
  • payment application
  • database
  • firewall
  • identity provider
  • Windows
  • Linux / SSH
02 · nano
  • Collect and parse
  • Detections and alerts
  • Search and cases
03 · Your storage
  • Disks you own
  • Optional object storage tier
  • Retention you set
Optional · AI pivt AI calls your model endpoint directly: any OpenAI-compatible API (including self-hosted models) or the Anthropic Messages API. Off by default; model calls never go through nano.
nano, the vendor

Never receives your logs.

Connected
  • Daily license check-in: deployment ID, install ID, version
  • Hourly content and enrichment-feed updates (no data sent; can be turned off)
  • One number per day: total GB ingested
  • Downloads: log-source catalog, detection rules and SOAR content, enrichment feeds, releases
Air-gapped
  • No connection to nano at all
  • Offline license file, renewed by hand
fig 01 · nano runs inside your environment. Log data is never sent to nano.
Retention

A year, or longer.

Event retention is yours to set (365 days by default). For PCI DSS, set at least 366 days, or 13 months, so a full 12 months is always kept. Keep recent months on fast disk and tier older data to your own object storage. Storage and retention

Licensing

Priced per GB/day, not per month kept.

The license is priced on daily ingest, so keeping a year or more costs you storage, not license. Every license includes every feature.

No standing access

nano never holds your logs.

nano has no standing access to your install. Support sees only what you choose to share. A connected install sends a daily license check-in and one GB/day number; air-gapped installs send nothing. Air-gapped deployment

FAQ

Questions we get asked.

What is PCI DSS Requirement 10?

Requirement 10 of the Payment Card Industry Data Security Standard is about logging and monitoring all access to system components and cardholder data. It covers which events are logged and what each entry records (10.2), protecting logs (10.3), reviewing them (10.4), keeping them (10.5), time synchronization (10.6) and detecting failures of critical security controls (10.7).

How long does PCI DSS require logs to be kept?

Requirement 10.5.1 requires audit log history to be kept for at least 12 months, with at least the most recent three months immediately available for analysis. Older logs can sit on cheaper storage, as long as they can be produced when needed.

Does PCI DSS v4 require automated log review?

Yes. Requirement 10.4.1.1 requires automated mechanisms to perform audit log reviews. It was a best practice until 31 March 2025 and is now mandatory. A SIEM running detection rules on incoming events is the usual way to meet it.

What changed for logging on 31 March 2025?

The 51 future-dated requirements of PCI DSS v4.x became mandatory. For logging, the main ones are automated log review (10.4.1.1), a targeted risk analysis to set how often other components' logs are reviewed (10.4.2.1), and detecting failures of critical security control systems, including audit logging, for all entities rather than only service providers (10.7.2).

Does PCI DSS require a SIEM?

Not by name. It requires centralized, protected logs, automated daily review, a year of retention with three months immediately available, and alerts when logging fails. A SIEM is the common way to do all of that in one place.

Is nano a PCI DSS service provider?

Not for your logs. nano, LLC, the vendor, never receives your logs and has no standing access to your install. The nano software you run is different: it stores and processes whatever your sources send it. If a source logs full card numbers, your nano install holds account data and is in your CDE scope. Mask or drop PAN at the source, and confirm scope with your QSA, who assesses the SIEM as part of your environment.

Is nano PCI DSS compliant or certified?

PCI DSS assesses your environment, not the tools in it. nano, LLC holds no PCI DSS attestation and no PCI SSC listing for nano. It is the SIEM you run to collect, protect, review and keep the logs Requirement 10 asks for.

Should card numbers appear in our logs?

Logs should not become a new store of account data. Configure sources not to log full card numbers or sensitive authentication data, and treat any log that does as cardholder data. If a source does log PAN, your nano install holds account data and is in CDE scope; because it runs in your environment, that data at least stays inside the boundary you already control.

Primary sources

Read the rules yourself.

Start with nano.

From US$149/month at 5 GB/day, US$279/month at 10 GB/day (list price, billed monthly; 10% off billed annually). Every feature in one license, and one license covers two installs.

Buy nano
Talk to sales