Saltar al contenido

Ridgeline Cyber

@ridgelinecyber.bsky.social did:plc:3qcbg55bbfqd5qtkft2vf3jv

Microsoft 365 Security, Detection Engineering & Incident Response Training ➔ http://ridgelinecyber.com/training/courses

En Bluesky desde el

Seguidores
26
Siguiendo
14
Posts
15
Días en rankings
0

Resumen

Ridgeline Cyber (@ridgelinecyber.bsky.social) es un usuario de Bluesky que se unió el 10 octubre 2026. Tiene 26 seguidores, sigue a 14 cuentas y ha publicado 15 posts.

Apariciones en rankings

Los mejores días en que los posts de esta cuenta entraron en la lista diaria de Debya.

Esta cuenta aún no ha aparecido en un ranking diario.

Posts que le gustaron recientemente

Me gusta públicos de la red Bluesky.

  • RootGuard Security@rootguardsec.bsky.social

    A registered FIDO2 key does not prove your break-glass account works. Can the responder retrieve the key? Can they authenticate from the emergency workstation? Can they access the admin centre? Does the SOC receive an alert? Test the recovery path, not just the configuration.

    Ver post
  • RootGuard Security@rootguardsec.bsky.social

    Privacy obligations continue to grow, and AI is tightening the link between privacy, governance, and risk. Orgs must demonstrate lawful bases, transparency, and controls over training data and automated decisions. Siloed privacy struggle when AI systems and third parties expand the data surface.

    Ver post
  • RootGuard Security@rootguardsec.bsky.social

    Fraud and scams are accelerating partly because adversaries are industrializing AI, automation, and crypto. Ransomware-as-a-Service, social engineering, account takeovers, and investment scams are rising faster than legacy compliance systems can respond. Compliance is now a technology arms race.

    Ver post
  • RootGuard Security@rootguardsec.bsky.social

    Third-party risk is still a top weak link. Concentration risk, sub-processor blind spots, and stale questionnaires drive incidents. Regulators and boards now expect continuous monitoring, not annual attestations. TPRM needs GRC integration, clear ownership, and real evidence.

    Ver post
  • RootGuard Security@rootguardsec.bsky.social

    Blocking device code flow? Check who’s using it first: SigninLogs | where TimeGenerated > ago(30d) | where AuthenticationProtocol =~ "deviceCode" or OriginalTransferMethod =~ "deviceCodeFlow" | summarize count() by UserPrincipalName, AppDisplayName

    Ver post

Inicia sesión para ver más

Cuentas que bloquea

En Bluesky los bloqueos son registros públicos.

Esta cuenta no bloquea a nadie.