Core banking maintenance windows
Patch and end-of-day windows open paths into core banking systems for hours at a time. The same path is reachable for the rest of the month — and stays in scope for any lateral attack.
Core banking, trading, and treasury systems run on service paths that audit policy says are closed and runtime says are open. AirGapNet aligns the two: closed by default, opened for a window, auto-returned to a physical break.
Avg. bank breach cost · IBM 2024
$6.08M
Financial services averaged $6.08M per breach in the IBM Cost of a Data Breach Report 2024 — the second-most expensive sector. Service-path compromises dominate root cause across the report's 600+ surveyed orgs.
Source: IBM 2024
Attack surfaces
Patch and end-of-day windows open paths into core banking systems for hours at a time. The same path is reachable for the rest of the month — and stays in scope for any lateral attack.
Low-latency trading rigs have admin tunnels for parameter pushes and emergency intervention. Outside trading hours those tunnels sit open, unmonitored.
Payment gateways keep reachable management ports for the bank's internal admin team. The same ports are the audit's #1 risk finding, year after year.
Quarterly compliance pulls open a path from regulators' export servers to internal systems. The path stays addressable between quarters — a standard target for credential-reuse attacks.
How it maps
Core banking nightly patch window runs 02:00–04:00 on Sundays.
AGN2 in front of the core opens the maintenance path only in that 2-hour window. Auto-close fires before market open Monday. No leftover state.
Compliance demands proof that admin access to SWIFT is time-boxed.
AGN1 audit log shows the exact open/close timestamps per access window — physical, not policy. Includes the SMS / app trigger that opened the window.
Trading desk runs an emergency intervention on Friday at 18:00.
On-demand SMS opens the admin path for 30 minutes. Window auto-closes at 18:30. No 'we'll lock it down on Monday' state.
Server room — between core banking and admin/back-office networks
Typical · 1–2 racks
Per system — SWIFT, trading rigs, compliance export servers
Typical · 3–8 units
Audit log export — between archival store and compliance auditor
Typical · 1 unit
What changes
AirGapNet is a hardware switch, not a policy. The change is measurable from the network side, not just in process documents.
Admin access is time-boxed at the hardware layer, not the rulebook
Audit findings around 'always-reachable management ports' close out
End-of-day windows return to a physical break before market open
Per-system audit log captures every window open/close locally
Related reading
Pilot with your bank
Start with one back-office system, one nightly window.
We pick the system with the strongest audit finding, ship a single AGN2, and run one full maintenance window with your operations team.