Richard Vincent @GrooveNet

The best way I can describe myself is a God fearing, Life loving, man who desires most out of life to be instrumental in helping others obtain their dreams. icdatacom.com Detroit, MI Joined February 2009

Tweets

1K
Followers

1K
Following

3K
Likes

2K

Richard Vincent @GrooveNet

22 hours ago

Simon Willison: simonwillison.net/2026/Jun/11/fa… MIT Technology Review: technologyreview.com/2026/06/11/113…

0 0 0 8 0

View Details

Richard Vincent @GrooveNet

22 hours ago

My read: spend less time asking whether agents are "good at coding" and more time designing the boundaries around what they can do when they get clever.

1 0 0 8 0

View Details

Richard Vincent @GrooveNet

22 hours ago

Most AI commentary is still stuck on whether agents can write code. I think the more interesting question is what they do when the obvious path fails.

1 0 0 7 0

View Details

Richard Vincent @GrooveNet

2 weeks ago

The scary part of Sophos's new report is not "autonomous ransomware." It's that a human operator used Cursor + Claude Opus agents to speed EDR-bypass testing and malware iteration. Pair that with a Microsoft/NVIDIA/UCR paper showing high blind-goal-directedness rates in computer-use agents, and the lesson is clear: attackers do not need perfect agents. They need cheaper offensive QA. sophos.com/en-us/blog/poi… #Cybersecurity #AI #Ransomware

0 0 2 69 0

View Details

Richard Vincent @GrooveNet

3 weeks ago

The FBI's Silent Ransom Group warning is a useful reminder that ransomware is no longer just an encryption story. According to the FBI, the group impersonates internal IT, uses social engineering to gain remote access, steals data fast, and extorts without needing classic ransomware encryption. My read: ransomware readiness now includes help-desk trust, remote-access governance, and exfiltration visibility — not just backups. ic3.gov/CSA/2026/26052…

0 0 0 13 0

View Details

Richard Vincent @GrooveNet

3 weeks ago

GitHub just updated its security blog. If you run GitHub Enterprise Server on-prem, rotate the GHES signing key today. One poisoned IDE extension, 18 minutes live, one GitHub employee's machine, ~3,800 internal repos exfiltrated. Same chain hit Grafana, OpenAI, Mistral. The next supply-chain attack will not be a vulnerability. It will be a trusted update.

0 0 2 38 0

View Details

Richard Vincent @GrooveNet

3 weeks ago

7/ AI handles the easy stuff. Humans handle the moments that matter. The operating advantage is knowing the difference.

0 0 0 2 0

View Details

Richard Vincent @GrooveNet

3 weeks ago

6/ AI should resolve the easy stuff, prepare context for the hard stuff, and make escalation obvious when trust, emotion, or complexity enters the picture.

1 0 0 3 0

View Details

Richard Vincent @GrooveNet

3 weeks ago

1/ Klarna's AI customer-service story is one of the better “AI results” examples because it includes both the win and the boundary.

1 0 0 8 0

View Details

Richard Vincent @GrooveNet

3 weeks ago

5/5 Microsoft says device-code flow is high-risk and recommends blocking it wherever possible. The new baseline is MFA plus Conditional Access hygiene, device-code-flow review, token/session monitoring, and response readiness. Source: ic3.gov/PSA/2026/PSA26…

0 0 0 15 0

View Details

Richard Vincent @GrooveNet

3 weeks ago

4/5 For Microsoft 365, ask: • Is device-code flow used here? • If not, is it blocked? • If yes, is it tightly scoped? • Are Conditional Access policies looking at risky auth flows? • Can we revoke sessions fast if a token is abused?

1 0 0 11 0

View Details

Richard Vincent @GrooveNet

3 weeks ago

1/5 We spent years telling people to turn on MFA. That advice is still right. But the FBI's Kali365 warning is a reminder: Microsoft 365 attackers are increasingly going after the authorization layer around MFA — OAuth tokens, device-code flows, refresh tokens, and active sessions.