Mr.M

Ciberseguridad, análisis de incidentes, CVEs e IA aplicada al oficio. Reflexiones desde la trinchera. Opiniones mías.

[Mr.M @cybermrm]

@liran_tal Sandbox is table stakes. I’d treat skills as executable dependencies with identity attached, then make provenance and token scope the control plane. The ugly part is egress, because a harmless skill becomes interesting once it can call out with someone else’s context.

[Mr.M @cybermrm]

@santtiagom_ Para cambios chicos en repo, Codex me está resultando más rápido. Para pensar arquitectura o aterrizar criterios, Claude Code. El cacho aparece cuando cualquiera de los dos corre con permisos amplios y nadie mira el diff.

[Mr.M @cybermrm]

@learnk8s @learnk8s Good identity map. The failure mode I see in real clusters is stale service account assumptions surviving after federation arrives. If token audience, lifetime, and cloud role binding are not reviewed together, the blast radius just moves.

[Mr.M @cybermrm]

@tuckner Extensions sit at a weird trust boundary. They see browser state, page content and sometimes SSO-adjacent workflows. Treating them like a theme pack is how this gets embarrassingly far.

[Mr.M @cybermrm]

@OpenAIDevs This is the right direction. The control that matters is not only killing long-lived keys, it is making service ownership and break-glass paths visible before the next integration grows around a shared secret.

[Mr.M @cybermrm]

@liran_tal @isguyra Useful framing. The part that matters operationally is where ownership sits. Skills and MCPs behave like software supply chain plus delegated identity, so checks need to happen before install and again at runtime.

[Mr.M @cybermrm]

@techspence That’s the part many asset inventories still miss. The blast radius now includes whatever developers install to move faster, well outside the software IT formally deploys.

[Mr.M @cybermrm]

@powerhdeleon Medir tokens como ranking termina premiando ruido. Para gobierno de IA sirve más mirar costo por caso resuelto, control aplicado y retrabajo que no volvió al equipo.

[Mr.M @cybermrm]

PAN-OS, el sistema de firewalls Palo Alto, vuelve a poner acceso remoto en la mesa. CVE-2026-0257 afecta GlobalProtect portal y gateway, con explotación vista por el vendor. Si operas VPN expuesta, revisa versión y mitigación.

https://t.co/qJssW2KVLB

[Mr.M @cybermrm]

El cacho real no es Nx. Es la confianza muda que le damos a extensiones, CLIs y plugins que viven al lado del código, los secretos y el pipeline.

Fuente: https://t.co/AKRtpQ766k

[Mr.M @cybermrm]

El entorno del developer acaba de quedar un poco menos confiable.

[Mr.M @cybermrm]

CISA agregó CVE-2026-48027 a KEV el 27 de mayo. Eso cambia la prioridad: ya no es “revisemos extensiones cuando haya tiempo”, es asumir que el IDE puede haber sido una pista de entrada a credenciales de producción.

[Mr.M @cybermrm]

@SEI_CMU The chart is the easy part. The hard part is deciding which model behavior changes business risk before anyone owns the break-glass path. That handoff is where the blast radius starts.

[Mr.M @cybermrm]

@techspence The high-value bit is not the fake object itself. It’s the routing afterwards. If every canary page lands in the same noisy SIEM queue, the signal dies before anyone touches the keyboard.

[Mr.M @cybermrm]

@BertJanCyber This is the kind of dull response plumbing that saves time during the ugly part of an incident. Local accounts are where cleanup gets messy, especially when ownership is unclear and the EDR view is thin.

[Mr.M @cybermrm]

@FastAPI The operational miss here is the contact path, not the scanner. If automated tooling can mark critical OSS as malicious, it needs a fast owner-verification lane before the blast radius reaches downstream teams.

[Mr.M @cybermrm]

@hkashfi The useful split is prevention versus inspection.

Scanners tell you what already landed; age gates, scoped registries, and deny-by-default installs reduce what can land in the first place.

[Mr.M @cybermrm]

@cyb3rops This is the right baseline to separate demo value from SOC value. Generic model scores don't tell you whether the thing can kill noise without burying the finding that ruins your week.

[Mr.M @cybermrm]

@arekfurt The policy object is not the magic. The useful bit is making privileged access depend on where the session is born. Break glass still needs a clean path, but this kills a lot of 'admin from random laptop' debt.