Security architecture · cloud security · platform design
Fractional CISO Advisory for Mid-Market Teams
Know what to fix first, who owns it, and what evidence will show it’s done. Get executive guidance on security and AI readiness while your team stays in control of implementation.
- Enterprise experience
- IBM Cloud assurance and financial-services security
- Design focus
- Connect security signals, business context, and controls
- Personal portfolio project
- Explore Exposure Control: AI-assisted, synthetic, non-production
“Alfe is a skilled security and compliance professional.”
“His work is meticulous and conclusions are well-developed.”
Start here
Professional experience. Personal projects.
A case study from my professional experience, followed by a personal project that demonstrates my approach to security design.
Cross-team vulnerability leadership
From open-source software (OSS) and containers to applications and infrastructure: coordinating owners, technical context, urgent work, and evidence.
Read case study →Personal portfolio projectExposure Control
A small-scale project I built with AI assistance to explore an enterprise challenge: turning vulnerability findings into priorities, owners, and verified closure. Uses fictional data, not employer or client work.
Explore personal project →Questions about my synthetic project? Open ASTA Guide
Consulting
Fractional CISO advisory
Five advisory hours each month for policy, vulnerability and vendor-risk priorities, plus a separate quarterly strategy review. Give leadership a short list of decisions and your delivery teams a clear action plan.
Best for organizations with an executive sponsor and an internal team or provider that can implement fixes. Advisory does not include live monitoring, incident response, production changes, or compliance sign-off.
Share your goals and project needs. Keep credentials and sensitive data out.
Remediation governance: Start with your existing vulnerability or cloud findings. We’ll agree on the priority, recommended owner and closure criteria for the issues that matter most.
AI security readiness: Review proposed AI use cases before rollout. Clarify data access, provider safeguards, business ownership, human review, and what leadership needs to approve.
Experience and credentials
Experience and results.
ISC2 CISSP and Microsoft Certified: Azure Fundamentals.
Experience in finance, technology, and U.S. Navy submarine service.
Alfe Corona · Selected experience
Work delivered at each organization.
Remediation coordination, audit readiness, and testing documentation.
- Wells Fargo
Coordinated urgent hardware security module (HSM) vulnerability remediation with technical owners; tracked owners, due dates, escalation, and closure evidence. Technical teams implemented and validated fixes.
- IBM
I led SOC 2 audit readiness for IBM Cloud’s Cloud Shell, CLI, and Developer Experience teams, working with engineers and PwC auditors.
- Google
I created a step-by-step email QA guide for Google Maps Local Guides with developers and the program manager.
- U.S. Navy
I maintained 99.6% inventory validity. Also earned the Navy and Marine Corps Achievement Medal.
Professional recommendations
What colleagues and leaders say.
Perspectives from people who have managed my work or collaborated with me.

Caryn Woodruff
Former direct manager
“Alfe is a skilled security and compliance professional. He possesses excellent problem-solving and analytical skills and is able to effectively identify and mitigate potential risks and vulnerabilities.”

Ami Diaz, CRISC, CDPSE
Former direct manager
“His work is meticulous and conclusions are well-developed. He also shares insights and best practices with his peers. He was a great asset to the team.”

Ryan Inagaki
Former colleague
“During his tenure, I was consistently impressed by his deep understanding of the industry's best practices and regulations.”

Joel Pichardo
Cybersecurity peer
“Alfe is the kind of cybersecurity expert you hope to have on your team.”
Operator perspective
Enterprise experience
After my Wells Fargo role ended in October 2026, I launched my independent advisory practice. At Wells Fargo, I coordinated remediation across up to 15 teams and built a tracker covering 200+ applications. At IBM Cloud, I led SOC 2 audit readiness for three teams. Today I bring those lessons to security priorities, executive decisions, and AI adoption planning for mid-market organizations.
I connected technical findings with accountable owners, investigated Prisma–Qualys reporting differences, and escalated urgent blockers. I also improved repeatable reporting workflows and trained colleagues.
- Technical owner
- Identified
- Remediation date
- Agreed
- Status and escalation
- Documented
- Remediation and validation
- Status reconciled

Security leadership perspectives
CyberTainment TV
Videos on vulnerability priorities, remediation ownership, and the evidence needed to confirm closure.
Watch the series on YouTubeFeatured episode
Why Your Vulnerability Spreadsheet Is the Breach.
ExploitabilityAffected systemsValidation checksWatch episodeApproach
How I work.
I review finding evidence and business context, agree on remediation owners and next steps, and check whether the closure criteria were met.
Connect findings to assets and owners
Check evidence before escalation
Prioritize by exploitability and business impact
Agree on owners, deadlines, and closure checks
Direct answers
How prioritization and closure work.
What is cyber exposure architecture?
In this portfolio, cyber exposure architecture connects vulnerability findings to affected assets, business importance, controls, and remediation owners. Exposure Control demonstrates these links with fictional data.
How do organizations prioritize vulnerabilities by business risk?
Consider exploitability, whether the asset can be reached, its business importance, data sensitivity, and existing controls. Assign an owner and use those factors to decide which findings need attention first.
How does exposure control connect engineering, architecture, and executives?
The synthetic Exposure Control project shows finding priorities, affected applications, remediation owners, and closure checks. Engineers and leaders can inspect the same records when deciding what to fix and what remains open.
What does evidence-gated closure mean?
Closure requires validation data confirming that the finding was resolved or meets an approved control criterion. Without that evidence, the finding stays open or returns to remediation.
Explore my synthetic Exposure Control project.
Connect
Start a conversation.
Tell me the role, project, or speaking topic. Include the next step. Keep confidential information out.
Send me the context
