Prasen Shelar

Documenting the founder path. From 0→1 in startups, relationships & everything in between. Helping others break into tech & stay human doing it.

[Prasen Shelar @PRaSeN_S]

@Ldataengineer The same split helps at the other end. Whoever marks a finding as fixed shouldn't be the only one confirming it, so a separate check before the ticket closes catches the fixes that didn't actually hold.

[Prasen Shelar @PRaSeN_S]

@saxenism For anyone running this across a team's cloud, ask it to put a named owner and a date next to each unresolved issue it logs. Without that, the log tends to become a list nobody opens again.

[Prasen Shelar @PRaSeN_S]

"We couldn't hire more people; we hired Axari."

Nikhil Sud, CIO at Boyd Corp.

Most security teams can't hire their way out of the backlog. Axari gives every person on the team an AI Twin that finds the owner and chases the follow-ups.

https://t.co/elCgwLyfnz

#CISO #cybersecurity

[Prasen Shelar @PRaSeN_S]

@a16z A practical use of that window: pick one internet-facing app and time an emergency patch end to end, from the advisory landing to someone confirming the fix is live. Whichever step takes longest is the one to sort out before the next php2shell.

[Prasen Shelar @PRaSeN_S]

@levie The patching part is where it piles up. As agents find bugs faster, someone still has to work out who owns each system, get a change window and check the fix held. Security leaders I speak with already have more findings than people to close them.

[Prasen Shelar @PRaSeN_S]

Keep your tools. Add a Twin. https://t.co/Tzd9DfTIwW

[Prasen Shelar @PRaSeN_S]

Top 5 tools every security pro needs in 2026: Wiz, Snyk, Vanta, Jira. And the one that gets the work finished. 👇

[Prasen Shelar @PRaSeN_S]

Who's keeping your CISO up at night? Not hackers.

Read to the end, then check who sent "any update?"

https://t.co/Tzd9DfTIwW

[Prasen Shelar @PRaSeN_S]

Free tools find it. Your Twin moves it to done. https://t.co/Tzd9DfTIwW

[Prasen Shelar @PRaSeN_S]

5 security tools you can start using free today: Prowler, Trivy, CISO Assistant, Plane. And the one that gets the work finished. 👇

[Prasen Shelar @PRaSeN_S]

Chat AI helps you think. An AI agent stays with the work: finds the owner, follows up, and brings you in only when judgment is needed.

Try it on one workflow: https://t.co/Tzd9DfTIwW (50,000 credits free for 30 days, no credit card required).

[Prasen Shelar @PRaSeN_S]

Security teams aren't short on tools. They're short on people to finish what the tools find.

Here's why defenders are moving from AI chat to AI agents, and the guardrails to demand before you let one in. 👇

[Prasen Shelar @PRaSeN_S]

CrowdStrike found criminal groups running AI agents in real intrusions.

The advisories took a day. The fixes take weeks.

Axari helps you get there faster. https://t.co/Tzd9DfTIwW

[Prasen Shelar @PRaSeN_S]

This week in security: 4 incidents and 4 fixes.

• PHP2Shell: patch PHP to 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35
• LiteLLM 1.107.0 backdoored: rebuild, rotate keys
• ConnectWise → M365: review app access
• AI agents in real intrusions 👇

[Prasen Shelar @PRaSeN_S]

@ZackKorman Finding them took a scan. Fixing them means tracking down who owns each server, getting a maintenance window, patching, then checking again that the old PHP version is really gone. An owner name on every asset record makes that week a lot shorter.

[Prasen Shelar @PRaSeN_S]

@techspence A lot of those basics have no owner. Nobody on today's team created the old test accounts, so nobody feels they're theirs to remove. Sending each system owner a list of accounts unused for 90 days, with a keep-or-delete date, catches a lot of them.

[Prasen Shelar @PRaSeN_S]

@tdemesquita When you ask for that budget, a short list usually lands better than the category: which systems still lack MFA, which critical patches are past your own policy, who owns each one, and the date of the last test restore.

[Prasen Shelar @PRaSeN_S]

@chrislciaba Part of the problem is that each company writes its own controls, so the report mostly shows you did what you said you would. If you're reviewing a vendor, skip the opinion letter and read the exceptions the auditor found and how long the test period was.

[Prasen Shelar @PRaSeN_S]

@SecBustersInc For a vendor-hosted app I'd still call the internal business owner first. They decide when downtime is OK, and the vendor usually waits for someone on your side to sign off. Worth writing that one name next to each vendor app before the next emergency.

[Prasen Shelar @PRaSeN_S]

@MattLenhard A test I like: take your last five critical findings and show who owned each, when it was fixed, and how someone confirmed the fix held. That follow-through is what I'm building for, and it's the weakest spot for most security teams I talk to.