An Australian payment-gateway provider, regulated as a financial-services business and subject to card-scheme obligations, operates Secure60 in production across its transaction, network and corporate environments.
The provider ran separate tools for log collection, detection, vulnerability scanning and compliance tracking, each holding part of the evidence. When the regulator, a card scheme or an acquiring bank asked for evidence that a control operated, the answer was assembled by hand from all four, and the same requests recurred each audit cycle.
Transaction and cardholder-environment logs had to stay in Australia, and retention had to satisfy both the regulator’s expectations and the card-scheme audit window.
Secure60 replaced the four tools with one platform in the Australian region. Log Management holds the transaction, network and corporate telemetry; SIEM runs the managed rule library over it; Vulnerability Management tracks exposure across the same asset set; Governance maps the evidence from all three to the controls the regulator and the card schemes examine.
Because the capabilities share one context, a detection references the vulnerability state of the host it fired on, and the control evidence draws on the same records the analysts use. The provider’s team operates the platform, with Secure60 experts engaged for tuning and audit preparation.
Evidence is available when a request arrives, so preparation for each cycle is a review of existing records measured in days rather than a project measured in weeks.
Four renewals became one, with licence and infrastructure spend reduced accordingly and a single contract to manage.
Analysts see the host’s vulnerability state next to the detection rather than switching tools.
The customer is available as a reference on shortlisting, under NDA.
