Jason M.
Pickering, Canada · Strategic Information Security Leader Championing Quantified Risk Analysis and Security Process Improvement. · Arancia
University of Toronto
5 followers
About
I've spent 27 years in information security, long enough to watch the field cycle through the same mistakes under new names. My work is about not repeating them.Security is a risk management function, and risk is only useful when you can actually reason about it. I build programs around quantified risk (FAIR), not qualitative heat maps and maturity scores that feel rigorous and aren't. I would rather hand a board a defensible loss-exceedance curve than a colour on a grid.What I do, in practice:• Build and run security functions end to end, from architecture to board reporting, organized around what measurably reduces risk rather than control catalogues and audit calendars.• Quantify cyber risk in financial terms, so security investment gets decided the way every other business decision does. (I pioneered a FAIR-based practice and ran 50+ quantified assessments across financial services, healthcare, government, insurance, and higher education.)• Treat governance as stewardship, not compliance theatre: the discipline of deciding what the program is for, and what it will not do, before an incident forces the question.I am skeptical of folk security, i.e. advice that survives by repetition rather than evidence; best practices nobody has verified, and frameworks mistaken for foundations. I write about this as The Infosec Stoic on Substack (https://infosecstoic.substack.com/) Background: MEng (Toronto, information security), BASc (Waterloo, computer engineering), CISSP, CRISC, OpenFAIR. Twenty-seven years from network engineer to senior security leadership.If you think clearly about risk and want a security program that earns its budget, we will get along.
Skills
- Application Architecture
- Assessment
- Business Continuity Planning
- Campaign Development
- Certified in Risk and Information Systems Control (CRISC)
- Cloud Security
- Communication
- Compliance Auditing
- Compliance PCI
- Computer Engineering
86 skills in total
Licenses & Certifications
-
Certified in Risk and Information Systems Control
ISACA
Issued Jun 2026
-
The Open Group Certified: Open FAIR™ Foundation
The Open Group
Issued Jun 2015
-
Certified Information Systems Security Professional
ISC²
Issued Mar 2005 · Expires Mar 2029
Experience
-
Senior Security Consultant
Arancia
Mar 2025 — Present
-
Solution Architect
Computacenter
Jul 2020 — Oct 2024
Greater Toronto Area, Canada
-
Senior Manager Cyber Security
MNP Digital
Apr 2010 — Jun 2020
Toronto, Ontario, Canada
8 experiences in total
Education
-
University of Toronto
Master, Computer Engineering
Jan 1998 — Jan 2001
-
University of Waterloo
Bachelor, Applied Science
Jan 1992 — Jan 1997
Recent posts
In the programs I've assessed, the security model is one nobody chose, and it's usually a framework.
Phil Venables recently wrote down ten questions a CISO's management tool should be able to answer. I held them against two explicit models. Against Rick Howard's five strategies, half are Risk Management and none is mainly Active Defence. My guess at why: detection and patching get answered in the SOC's and engineering's own tools. Against O-ISM3's process groups, half are Strategic, half Tactical and none Operational. None sits in O-ISM3's Generic group either, where the processes that act on the program itself live, so nothing asks outright whether the program is built right or what it has learned since last year. That looks like a real gap.
The ten also presuppose a model of the business: which processes are critical, which suppliers they depend on, where the revenue comes from. The CISO usually doesn't hold that, and in some organizations nobody does.
So pick your model on purpose (Howard, O-ISM3 or FAIR-CRMP) and check that it fits the business you're in as well as the security program. Get the model right and you'll know whose data you need to answer each of Phil's ten. Without it, the budget follows the audit cycle and nobody can say why.
The CFO's model (three statements, double-entry bookkeeping) took a few centuries to settle. The CISO title is about thirty years old, and most of us are still running a model we absorbed and never examined.
https://infosecstoic.substack.com/p/the-choice-is-yours-pick-your-security
#CISO #RiskManagement #GRC
Another step outside the echo chamber. Venkatesh Rao offers an analogy for AI as a new kind of cell: model weights as a genome compressed from the internet, tools as proteins, humans as mitochondria supplying "liveness" (stakes, valuation, knowing which outcomes matter).
Ethan Mollick's four human advantages from Co-Existence map onto that: deep knowledge, wide knowledge, taste and agency. For practitioners the point is practical. Judging what matters, and catching a model that is confidently wrong, depends on knowing your field. That part doesn't migrate into the model.
https://www.panoptica.com/our-eukaryotic-moment/
#AI #InfoSec
There is a belief that RSI -> AGI -> Doom! Yuval Levin asks whether we're even on the path to AGI: AI progress is getting narrower, not more general, and recursive self-improvement would likely deepen that.
"The assumption that RSI would independently facilitate the emergence of a greater capacity for generality is invoked as a premise in many arguments about the future of AI, when in fact it is a proposition, and one that so far lacks much evidentiary or logical support."
Worth a read over the weekend, from outside the echo chamber.
https://www.thenewatlantis.com/publications/are-we-really-on-the-path-to-agi
#AI #AGI
Most business owners know the difference between a CFO, an accountant and a bookkeeper. One sets financial strategy, one keeps the books honest, one records the transactions. Hire the CFO when what you need is the bookkeeper, and you get excellent advice about ledgers nobody is keeping.
Security has the same ladder: vCISO, security operations manager, security analyst. Geoff Hancock's piece frames the choice as leadership versus delivery, and it is the right question to answer before signing a vCISO retainer. A vCISO can set direction, frame risk decisions and build the cadence. Without someone inside who owns the work, you get a roadmap and very little change in exposure.
You can outsource expertise, not responsibility.
https://saturdaycyberjournal.substack.com/p/a-vciso-wont-save-you-if-nobody-owns-51e
#vCISO #RiskManagement #infosec
I mostly stopped reading AI books; there's only so much "AI Doom" you can read. Co-Existence by Ethan Mollick is the exception, because it's about working with the AI we have today.
I think the most important idea is the jagged frontier. AI is very good at some tasks and poor at others, and the line keeps moving (Sutton's Bitter Lesson is a good reason to bet on it moving). If you tried it once, watched it fail, and wrote it off, you're working from stale data. And if you watched it succeed once and now trust it everywhere, you're trusting it well past what you've tested.
He names four human advantages: wide knowledge, deep knowledge, taste and agency. Taste and deep knowledge are what I judge its output with. Deep knowledge is what lets you know when the AI is confidently presenting something incorrect or slightly inaccurate.
So pick a piece of toil you know cold and work it with AI in each of his three modes: as a centaur (you set the goal and the method, and hand it the pieces you choose), as a cyborg (one tight back-and-forth loop), and as a conjurer (spawn agents, assign the work, evaluate what comes back). Check every output against what you know. That's how you find where the frontier sits for your own work.
Full review: https://www.goodreads.com/review/show/9045273195
#AI #InfoSec #BookReview