Custom software for ISAE 3402 and SOC reporting
A type II report doesn't assess whether your controls exist, but whether they worked throughout the entire period. That changes what you need to keep: not the situation on the day of the audit, but evidence from every month. If you gather it after the fact, you discover that the months when things went wrong are exactly the months for which nothing was kept.
Type I, type II and the difference that matters
ISAE 3402 is the international standard for assurance on controls at a service organisation, focused on controls that affect your customers' financial reporting. SOC 2 focuses on information security and the related system controls. Which of the two your customers ask for depends on what they engage you for.
The distinction that matters most is type I versus type II. A type I report assesses the design and existence of your controls at a single point in time. A type II report also assesses whether they actually worked over a period, in practice at least six months. That second part is what customers want, and it requires a very different kind of record-keeping.
For a Type I report, a description and a sample on the day itself are enough. For a Type II report, you must be able to show for every control that it was performed each time, with evidence from that period. An access review you carry out every quarter must demonstrably have been done four times, and a quarter in which it was forgotten cannot be fixed with an extra round just before the audit.
In a Type II examination, the auditor picks a random day from the period. That evidence must have been created at the moment of the activity, often in a server room or an archive room. How you capture it on site is covered in the app for signing off checks.
How we build this
The control and its frequency are the unit here. If the evidence is created automatically at the moment of execution, the audit becomes a selection rather than a search.
What you do, how often, who owns it and what the evidence is. Those four questions per control form the entire foundation; everything after that follows from them.
We pull it from the systems where the work happens rather than turning it into a separate task. Evidence that requires manual work goes missing in the busy months.
A control that was not performed once is a finding, not a disaster, provided you spot it yourself and act on it. Hiding it does not work; the auditor will find the gap.
What you assume of your customer belongs explicitly in the report. We build that as a list of its own, not as a paragraph nobody reads.
What the software actually does
The register of controls with their evidence underpins everything. Which components you need depends on whether you issue the report or receive it.
Controls with frequency and owner
For each control: what needs to happen, how often, by whom and what evidence it produces. Without those four, a Type II audit is a reconstruction after the fact.
Evidence from the systems themselves
Access reviews, backup checks, change approvals and log files come in through integrations rather than a round of emails. What arrives automatically does not go missing in a busy month.
Execution monitored per period
The system shows per control which periods are covered and which are not, during the period rather than afterwards. A gap can then still be fixed.
Exceptions with follow-up
A control that was not performed or a check that failed. Each becomes a finding with an owner and a deadline, because a gap you spotted and followed up yourself carries a different weight than a gap the auditor finds.
CUEC as an explicit list
The controls you assume of your customers, with a record per customer of whether they have confirmed them. This is the appendix everyone skips, and your own objectives rest on it.
Audit file per period
All evidence for the reporting period in one place, with the version of the control that applied at the time. At audit time, that is the difference between handing over and gathering.
Who we build for
Whether you issue the report or receive it changes the system completely. Four situations.
Service organisations that report
You issue the report to your customers and carry the full burden of proof. Your biggest risk is the month in which a control was skipped and nobody noticed. If you also fall under the Cybersecurity Act, part of your set of controls overlaps.
Outsourcing organisations
You receive reports from your suppliers and have to assess them. What you really need to read is the CUEC appendix, because it states what you should have put in place for their conclusion to hold.
Organisations with many suppliers
Dozens of reports a year, each with its own periods, its own exceptions and its own CUEC. Without a register, that becomes a filing cabinet nobody looks in until the auditor asks about it. Suppliers submit their reports via a supplier portal.
Chains where both roles meet
You issue a report and rely on your subcontractors' reports yourself. It then needs to be visible which part of your own assurance comes from their report. If a standard also underpins this, it ties in with your quality management system.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
The standards are revised periodically and your own set of controls changes with your services. Everything connected to that should be configurable and retained per version.
Why Appfront
Type II measures the period, not the day
We show coverage per period while it is still running. A gap you spot in month three can be fixed; the same gap in month nine cannot.
Evidence that collects itself
What people have to supply manually is exactly what goes missing in the busiest months. We pull it from the systems where the work happens.
The CUEC is not an appendix but an agreement
Your objectives are only met if your customer has set up their part. We turn that into a list with confirmation per customer.
A gap you find yourself carries different weight
We make exceptions visible with follow-up, because concealing them does not work and an auditor also assesses how you deal with deviations.
Security and privacy
An audit file contains the complete picture of how your organisation is secured, including the places where things went wrong at some point. To an attacker, that is more valuable than the systems themselves. We therefore restrict access tightly by role, separate submitting evidence from reviewing it, and log every time it is viewed.
Sharing with third parties raises a particular issue. Your auditor needs access, your customers want the report and sometimes the underlying documents, and your suppliers submit their own evidence. These are three separate circles that should not see each other's material. We therefore build separate access paths instead of one shared folder, and limit what an external party sees to the period and the controls they have been invited for. On the evidence side, a piece of evidence must be immutable and timestamped: evidence that can be updated afterwards is not evidence in a type II audit. How we handle security ourselves is set out in our information security policy; reports from outside go through our coordinated vulnerability disclosure policy.
Frequently asked questions about ISAE 3402 and SOC
A type I report assesses the design and existence of your controls at a single point in time. A type II also assesses whether they have worked over a period, in practice at least six months. Customers almost always ask for type II, and that requires evidence from every month rather than a snapshot.
ISAE 3402 focuses on controls that affect your customers' financial reporting; SOC 2 on information security and related system controls. Which one your customers ask for depends on what they engage you for; some service organisations issue both. Your auditor determines the scope, not your software supplier.
These are the controls that the service organisation assumes the customer has set up themselves, for example managing their own user accounts or checking output reports. The objectives in the report are only met if that assumption holds, and the report states this explicitly. It is the appendix that is skipped most often.
Read it, and in particular the exceptions and the CUEC list. The exceptions tell you what went wrong at your supplier; the CUEC list tells you what <em>you</em> should have set up for its conclusion to apply to you. Filing a report away without assessing those two gives false assurance.
Then it is an exception, and it belongs in the report. That is unpleasant but not fatal; what weighs more heavily is whether you spotted it yourself and what you did about it. A gap the auditor finds when you were unaware of it says something about your control environment, not just about that one month.
For a type I report, sometimes; for a type II, no. The question is whether the control was performed at the time, and a reconstruction after the fact does not answer that question. That is why we pull evidence from the systems where the work happens, rather than turning it into a separate task.
No. A certification states that you meet a standard; an assurance report describes your specific controls and an auditor's opinion on their design, existence and operating effectiveness. It gives your customers something a certificate does not: they can read exactly what you do.
It depends on the number of controls, how much evidence can be collected automatically, and whether the CUEC side needs to be included. The register with period coverage is usually usable quickly and immediately shows where the gaps are; the integrations cost more. We give a substantiated estimate after the discovery phase.
Collecting evidence during the period?
Take one control that you perform every quarter and try to find the evidence for four quarters back. Where that trail stops is where your type II risk lies. We build this as a standalone application and as part of a broader custom software engagement.