triox informatika

Compliance · SOX

IT operations under SOX

Since 2002, public companies listed on US stock exchanges have had to be able to prove that the IT systems behind their financial reporting operate in line with the laws and regulations overseen by the regulatory authorities. This regulatory framework also extends to the subsidiaries of these companies, including those in Hungary. Through our past clients, we have several years of operational experience in this area as well.

What SOX expects from IT

Under Section 404 of the Sarbanes-Oxley Act (SOX), management must assess the internal controls over financial reporting every year, and at larger companies an external auditor attests to this as well. On the IT side, these are the IT general controls (ITGC): who can access the systems and the data, how a change gets into production, and how continuous, recoverable operation of the systems is ensured.

The auditor does not ask for statements of intent, but for evidence: approvals, logs, review records, tested restores—for the entire period under review. So the question for an IT operator is not whether it does good work, but whether that work can be proven after the fact.

Where we have experience

In the SOX-scoped environments of past clients—international, publicly listed groups—we worked in the following four areas—from day-to-day operations to handling the external auditor’s requests.

Access

Access management

Documented granting and revoking of access, and periodic user access reviews—so that at any time we can show who has access to what, and who approved it.

The identity layer on our Security page →

Operations

Backup and restore

Daily verification of backups, restore tests with evidence, and operations logs—the question is not whether there is a backup, but whether it can be shown to restore.

Audit Restore Validation →

What is already built into our services

For us, a SOX-scoped environment is not a separate product. It is built on the same foundations that every client environment runs on:

  • A dedicated, isolated network environment and a dedicated gateway for each client—the network of your financial systems is shared with no one.
  • Multi-factor authentication, central access management, and a documented joiner and leaver process.
  • A management network that cannot be reached from the internet—only our authorized staff have access to the management interfaces.
  • Continuous monitoring, regular automated infrastructure audits and change tracking.
  • Documented restore tests with an audit-ready report.
  • Responsibility boundaries agreed up front: which controls are ours, which are shared, and which stay on your side.

The details are on our Security page, together with the responsibility matrix.

What we do not claim

We do not issue our own SOC 1 / ISAE 3402 report

We do not have an independent service organization control report. Instead, we offer what we have done before: we hand the evidence that the controls operate directly to your internal audit team and your external auditor, following their request lists.

Compliance is yours, the evidence is a joint effort

Your company’s management is responsible for SOX compliance. What we commit to is that the controls we operate work in a documented way, and that we can prove this to the auditor in full. Which control belongs to whom is set out in the contract up front.

We do not publish the names of our clients.

Let’s talk about what your auditor asks for

In an assessment, we go through which systems are in SOX scope, which controls we take on, and what evidence we need to deliver, and on what schedule.

Request an assessment