Facundo "Nick" Montefalcone
Cloud security architect. I build security functions, run cutovers that cannot fail, and write the tooling that proves controls work. 15+ years in security, and a theatre background that taught me to explain risk to any audience, from the boardroom to the SOC. Based in Buenos Aires, working remotely with US teams.
Zero Trust, DevSecOps and AI security automation across AWS, Azure and GCP.Self-reported results from prior roles.
Selected work
Taking security back in-house: an MSP exit on a 30-day clock
Revoked an outgoing provider's admin access across 19 systems in one weekend, with 0 hosts left on legacy remote tools and a SHA-256 evidence trail.
Building an in-house security function for a fintech
Six months leading security operations for a company of about 130 people: endpoint coverage, DLP tuning, leaver hygiene, SOC 2 support.
Information security assessment for an independent K-12 school
48 controls across 10 domains, a risk scale calibrated to a school, and a 12-month roadmap presented to the board.
Odoo Shield Warden: money-at-risk controls for Odoo
A controls engine I built for Odoo 18 and 19. It holds risky vendor payments for a second approver, groups fraud alerts into cases with a money total, and seals evidence in a SHA-256 chain.
Security Architecture Playbook: patterns & decision records
Vendor-neutral architectural blueprints, AI agent least-privilege scoping, API auth, PAM evaluation, and ADR templates.
What I do
How I work
Evidence first
Every figure in these case studies comes from my own working records or from tests you can rerun.
The written record is a control
Runbooks, trackers and minutes after every meeting. If it is not written down, it did not happen.
Client confidentiality
Client names and open findings are always withheld. I describe method and outcome, never a live weakness.