An IT operations center mid-incident review.
02 / 08 · Led by Andres
Practice area · 02/08

IT audit.

Controls testing across infrastructure, applications, and third parties. Scoped to the examination cycle, written to outlast it.

01

The practice

IT controls that pass examination — and stay passable.

Examiners ask 'show me.' We build for that.

IT audit is where most institutions discover their controls are theoretical. The policy says backups are tested quarterly; the evidence shows the last test ran in August. The access matrix says terminated users are removed within 24 hours; the report shows three accounts active four months past separation. We find these gaps before the examiner does.

Our scope covers infrastructure (servers, network, cloud), application controls (core banking, loan origination, payments), identity and access management, change management, vulnerability and patch management, data classification, and third-party / vendor risk. We run testing on a frequency that matches your examination cycle, with workpapers that travel.

This is the practice where the offshore team earns its keep. Testing 200 user-access samples is not work that requires a partner. Designing the sampling, reviewing the exceptions, and naming what they mean — that is.

02

What we do

The work in this practice, named.

01 · 06 Infrastructure controls

Server hardening, network segmentation, cloud configuration, encryption at rest and in transit.

02 · 06 Application controls

Input validation, authorization, segregation of duties, calculation accuracy in core systems.

03 · 06 Identity & access

Provisioning, deprovisioning, privileged access, periodic access reviews, MFA enforcement.

04 · 06 Change & release

Change tickets, approval workflow, segregation between development and production.

05 · 06 Vulnerability & patch

Scan cadence, exception tracking, remediation timelines, exemption governance.

06 · 06 Third-party / vendor risk

Onboarding diligence, ongoing monitoring, SOC report review, concentration risk.

03

A typical engagement

An IT audit cycle, end to end.

01
Weeks 1–2 Scoping

System inventory, control universe, prior-examination findings reviewed.

02
Weeks 3–10 Testing

Walkthroughs, sample selection, evidence requested, exceptions tracked.

03
Weeks 11–13 Findings

Exceptions analyzed, root cause named, severity rated, remediation discussed.

04
Weeks 14–16 Reporting

Report drafted, vetted with IT and management, presented to the committee.

04

Who leads it

The partner whose career is in this practice.

Andres J. Castañeda
Practice lead · IT audit

Andres J. Castañeda

Risk Advisory · Internal Controls · 27 yrs

Andres has run IT audit programs at banks, fintech sponsor-bank relationships, and Fortune 1000 institutions. He sits on the engagement for every examination cycle.

What this practice is not

We do not perform penetration testing or red-team exercises. Those are a different discipline, and we keep a short list of firms we trust to do them — happy to share names.

05

Related practice areas

What often runs alongside this.

Start an engagement

Bring the partners to the table.