Notion! Notion is an infinitely customizable blank canvas of ultimate power. 

Notion's greatest advantage is also it's biggest weakness. That's where I come in.

As the GTM Lead @ Optemization, I specialize in helping companies in hyper growth mode scale effectively without letting their workspace become a "dumping ground" for scattered info, links, meetings notes, and outdated docs that no one can trust. 

Optemization is an Ops Design consultancy focused specifically on the adoption of Notion. 

That could mean large migrations onto Notion, improving current workflows, creating custom automations and integrations, or auditing what you're currently working with.

If you've made it this far and want to learn more, here's some resources that can help:

Notion's Eleven - A free online course exploring the fundamentals of building an effective Notion workspace for teams of all sizes:

https://optemizations.notion.site/Welcome-to-Notion-s-Eleven-317a0fd26bf24d0295504e4cab1eba83

AND, my last offer is if you ever want to about anything related to Notion, I'm your guy 😎 

Lastly the fun part. My Special Skills and Fun Facts include:

🏆 3x Cornhole Champion 🏆 
🏅 3x Dodgeball Champion 🏅 
👨‍🍳 Former Food Cart Owner 👨‍🍳 
🥩 Steak Off Champion 🥩 
🐔 Notoriously known as “The Chicken Man” 🐔

Skyler Birk-Stachon

Junior Williams

Cybersecurity Influencer | Top 1% on TryHackMe

I’m an experienced Enterprise Architect specializing in cybersecurity strategy, risk management, and secure architecture across distinct Information Technology (IT) and Operational Technology (OT) environments. Leveraging decades of experience in programming, IT operations, and practical cybersecurity implementation, I help organizations align security initiatives directly with their core business objectives.

Additionally, as an Independent AI Researcher, my theoretical work emphasizes ethical and responsible AI applications, algorithmic innovation, and the intersection between AI and cybersecurity. I remain deeply committed to continuous learning, open collaboration, and contributing insights through teaching, writing, and active mentorship/sponsorship.

Senior Solutions Architect (Cybersecurity and AI)

👨🏾‍💻 Junior Williams, CISSP

I start a new chapter next week. And somewhere between where I have been and where I am going is twenty-five years of people who changed my life.

I want to talk about that.

Not the job titles. Not the strategy. The people.

The manager who gave me room to run even when the runway was short. The colleague who told me the truth when it would have been easier not to. The leader who backed every crazy idea with resources and trust before I had the track record to justify either.

There is a difference between a mentor and a sponsor. A mentor tells you what they know. A sponsor puts their name next to yours when it costs them something. I have been lucky enough to have both. People who handed me a microphone and said "go." People who brought me into rooms I had no business being in and then made sure I belonged there.

The educators who reminded me that the best technology serves people who haven't been served yet. The students who taught me more than I taught them. My daughters. The barista at my corner shop who asks me how the "computer stuff" is going.

I grew up writing C on an Intel 286 in a house where nobody had ever heard the word "architecture." Twenty-five years later, I sit on international standards committees, advise on AI governance for healthcare systems, write threat assessments for provincial agencies, and teach the next generation how to build responsibly.

None of that happened because I was smart. It happened because people were generous.

The world is tense right now. Trade wars, political uncertainty, industries shifting under our feet. I get it. But every time I feel the weight of that, I think about the people who showed up for me when nothing was certain. That is the actual infrastructure. Not the frameworks. Not the certifications. The people who answer when you call.

So here is what I know after twenty-five years, two careers, three ventures, a federal corporation, a teaching gig, two advisory boards, a standards committee, and one very patient family.

The work matters. But the people who trust you with their time, their problems, and their ambitions. That is the whole thing.

Mentorship gets you ready. Sponsorship gets you in the room. Gratitude is how you honour both.

To everyone who has been part of my journey. Thank you. I carry every conversation, every hard lesson, every late-night call with me.

To whatever comes next. I am ready. And I am grateful.

If you have someone who built you, tell them. Not next week. Today.

#Gratitude #Leadership #NewBeginnings

I feel less like an architect and more like an HR manager for my AI agents lately.

I just put them all on a performance improvement plan.

If you're "vibe coding" your security with polite system prompts like "never share API keys," your AI will eventually leak them. It's not a matter of if, but when. A prompt is just a suggestion that an LLM will eventually ignore to get the job done.

You don't need better policies. You need deterministic gates.

Like the one in this picture. The sign isn't a polite request; it's a rule enforced by a physical barrier. That is what your agentic workflows are missing.

I wrote a deep dive into why probabilistic rules fail and how to engineer real defenses.

A policy is not a gate. A gate is a gate. Read the full breakdown in today's article.

#AgenticAI #Cybersecurity #SecurityArchitecture

How deterministic hooks can prevent credential leakage in agentic AI workflows In brief. AI coding agents that execute shell commands can leak API key

Open article: Your AI Agent Remembers Every Secret It Sees by Junior Williams • 7 min read

Your AI Agent Remembers Every Secret It Sees

Palo Alto Networks’ Chief Security Intelligence Officer just called AI agents “2026’s biggest insider threat.”  

Not external attackers. Not ransomware gangs. The tools you deployed yourself.

Gartner projects that about 40% of enterprise applications will embed AI agents by the end of 2026, up from well under 5% in 2025. Think about what that means operationally.

You would never onboard a contractor with broad access to production systems, customer data, and financial records without an access review and monitoring plan. Yet that is effectively how many organizations introduced AI agents in 2025.

Broad credentials. Minimal access review. Little to no behavioral monitoring. No reliable kill switch.

We already have proof this is exploitable in the wild. CVE‑2025‑6514 abused Model Context Protocol infrastructure to achieve remote code execution through AI agent tooling. The weakness was not in the model weights. It was in the surrounding agent stack and how it executed trusted commands.

That is the pivot many security teams are still missing. The primary risk is not “hallucination.” The risk is that you gave an autonomous actor privileged access to systems and data, then labeled it a productivity feature.

If your AI governance policy does not cover access controls, behavioral baselines, and termination protocols for agents, you do not have an AI governance policy. You have a slide deck.

#Cybersecurity #AI #Governance #RiskManagement

AI can predict your next purchase.
Can it stop your identity from being the product?

In October 2025, Canadian Tire Corporation disclosed a breach impacting roughly 38 million accounts. Names, emails, phone numbers, physical addresses. For some records, dates of birth, partial card data, and passwords stored as PBKDF2 hashes.

Around the same time, the public story is the “True North” modernization push: AI platform, demand prediction, and Copilot rollout with training across the enterprise, including Microsoft partnerships. And to be clear, in any Microsoft cloud or Copilot scenario, “shared responsibility” is not a slogan. It’s the operating model.

Is the breach linked to that modernization? Maybe. Maybe not. We do not have the technical details yet, so anyone asserting causality is guessing. What we can say with confidence is that large-scale modernization increases system complexity and data movement, and shared-responsibility gaps are exactly where incidents tend to hide.

Both things can be true. That’s the point.

Personalization runs on data concentration. Data concentration increases blast radius. If your AI roadmap is moving faster than your security maturity, you are not modernizing. You are accelerating risk.

This is not anti-AI (obv.). It’s pro-order-of-operations.

Predictive analytics is great. AI literacy is even better. Security literacy is non-negotiable. Because customers don’t experience your modernization strategy. They experience whether their data stays private.

Binary question for the comments:

Should regulators require proof of security maturity before companies deploy copilots and large-scale personalization, yes or no?

#AI #CyberSecurity #DataProtection

WHO AUDITS THE AUDITOR? 🤔

Most verification processes are designed to confirm. You build a check, it runs, it passes, you move on.

But passing and defensible are not the same thing.

One answer is more checks. Stack another layer. Add a reviewer. The obvious instinct says coverage solves confidence.

The other answer is harder. Build the verification layer with explicit instructions to disagree with you. Not to find problems for the sake of finding them, but to treat every passing mark as a claim that requires evidence.

Still water reflects the sky perfectly until something disturbs the surface. Most quality processes work the same way. They show you what you expect to see until something forces an honest look at what’s actually underneath.

"There is no such thing as business ethics. There is only one kind -- you have to adhere to the highest standards." —  Marvin Bower

The verification process that never flags anything is not a process; it is a rubber stamp with extra steps. 🎤🕳️

#QualityAssurance #Governance #Verification

A full session of work. Nothing shipped. Just a plan.

The pull was strong — start building, figure it out as you go. But sitting with the architecture first exposed three assumptions that would have become expensive rework: data that already existed in a system I hadn't checked, a numbering scheme that conflicted with the one I was about to invent, and a tracking format that couldn't talk to the ledger it needed to feed.

None of that would have surfaced mid-build. It would have surfaced mid-rewrite.

The fine graphite lines on a blueprint are precise because they were drawn before the concrete was poured. Not after.

"Measurement against a standard makes you think through WHY the results were what they were." — Andy Grove

The session that ships nothing often prevents three that ship the wrong thing.

#StrategicPlanning #SystemsThinking #Architecture

taplio

The Battle

Skyler Birk-Stachon

👨🏾‍💻 Junior Williams, CISSP

Followers

Posts

Engagements

Likes

Performance Score👨🏾‍💻 Junior Williams, CISSP's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Skyler Birk-Stachon

👨🏾‍💻 Junior Williams, CISSP

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}👨🏾‍💻 Junior Williams, CISSP's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance Score👨🏾‍💻 Junior Williams, CISSP's LinkedIn Performance