ITKIT
Customs · 14 / 20
Customs Admin
Institutions, users, rules and audit for customs
From the problem to how we solve it
October 2026
Interactive prototype · synthetic data only
The problem
Who can do what?
1
Accounts of staff who changed post stay active.
2
Rule thresholds are changed by IT without a business sign-off.
3
No one can say who changed what, and when.
Who · Can do what · For which institution · Until when
ITKIT · Customs Admin · Prototype screens, synthetic data
The problem
Our answer
Customs Admin · designed to align with ISO/IEC 27001:2022 and NIST SP 800-53
The administration portal of the customs authority: institutions, users and roles, delegations, request types and workflow templates, detection-rule settings and integrations. Every change goes through maker/checker and lands in a full audit log.
How it works · 1 of 6
Onboarding
Partners, onboarded safely
Banks and exchange houses are onboarded step by step, and a second administrator approves go-live.
ITKIT · Customs Admin · Prototype screens, synthetic data
How it works
How it works · 2 of 6
Separation of duties
Conflicts blocked by design
Duties that must not mix are blocked by the system, not left to memory.
ITKIT · Customs Admin · Prototype screens, synthetic data
How it works
How it works · 3 of 6
Admins configure
Admins configure. They don’t decide.
Administrators configure the system. They never decide a declaration or a case.
ITKIT · Customs Admin · Prototype screens, synthetic data
How it works
How it works · 4 of 6
Workflows
Versioned workflows
Workflow templates are versioned. Open requests keep the version they started with.
ITKIT · Customs Admin · Prototype screens, synthetic data
How it works
How it works · 5 of 6
Maker and checker
Tested before it changes
A threshold change is back-tested and approved by someone who did not propose it.
ITKIT · Customs Admin · Prototype screens, synthetic data
How it works
How it works · 6 of 6
Audit log
Every change, on record
And every action is in a tamper-evident audit log.
ITKIT · Customs Admin · Prototype screens, synthetic data
How it works
What it includes
5 screens and workflows in the prototype
Audit log
Auditors and administrators; others see a permission-denied page
Institutions & users
System administrators at headquarters
Roles & separation of duties
System administrators and security officers
Workflow templates
System administrators and process owners
Detection rules (maker/checker)
Risk governance leads (checkers) and risk analysts (makers)
ITKIT · Customs Admin · Prototype screens, synthetic data
What it includes
Built to standards
International standards it is built to
| Standard | What it covers in Customs Admin |
|---|---|
| NIST SP 800-53 Rev. 5, AC-5 (Separation of duties) | Conflicting duties blocked by the system |
| NIST SP 800-53 Rev. 5, AC-5 (maker/checker for configuration) | Second person for rules and onboarding |
| ISO/IEC 27001:2022 (access rights and reviews) | Periodic access review |
| ISO/IEC 27001:2022 (privileged access) | Administrators under extra control |
| ISO/IEC 27001:2022 (access lifecycle) | Delegations with end dates |
| ISO/IEC 27001:2022 (change management) | Versioned workflow templates |
| ISO/IEC 27001:2022 (logging) | Tamper-evident audit log |
| WCO SAFE Framework 2025 (insider threats) | Administrators cannot act as officers |
We align with these standards; certification is issued by accredited bodies, not by ITKIT.
ITKIT · Customs Admin · Prototype screens, synthetic data
What it includes
Connects to
What Customs Admin works with
OneID (staff and institution sign-on)
Customs HQ, Port Operations and Bank Verify
ITKIT Anomaly Detection (threshold settings)
ITKIT ESP (integration registry)
SIEM / SOC (audit stream)
ITKIT · Customs Admin · Prototype screens, synthetic data
What it includes
Safeguards
What Customs Admin will never do
Administrators configure; they do not decide declarations or cases.
No change to rules, roles or thresholds takes effect without a second person.
ITKIT · Customs Admin · Prototype screens, synthetic data
Delivery
How delivery works
Start small, prove it, then scale and hand over
6–10 weeks
Assess
Map what already exists and decide, system by system: reuse, integrate, modernise or build.
4–6 months
Pilot
Customs Admin at one authority, with real users and a measured outcome, on national infrastructure.
12–24 months
Scale
Roll out by region and service, sharing identity, integration and audit.
Agreed per contract
Operate and transfer
We run it with your team, train them, then hand over operations, code escrow and keys.
Durations are typical ranges, fixed per contract
ITKIT · Customs Admin · Prototype screens, synthetic data
Delivery
Next step
See the administration screens in the prototype.
Customs Admin.
1 · Demo
A guided session on the Customs Admin prototype
2 · Assess
6–10 weeks to map what exists and fix the pilot scope
3 · Pilot
4–6 months with real users and a measured result
ITKIT · [contact name, email and phone]
Thank you