Aller au contenu

Ridgeline Cyber

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

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

Sur Bluesky depuis le

Abonnés
26
Abonnements
14
Posts
15
Jours dans les classements
0

Résumé

Ridgeline Cyber (@ridgelinecyber.bsky.social) est sur Bluesky depuis le 10 octobre 2026. Le compte a 26 abonnés, suit 14 comptes et a publié 15 posts.

Présence dans les classements

Les meilleurs jours où les posts de ce compte sont entrés dans le top quotidien de Debya.

Ce compte n’est encore apparu dans aucun classement quotidien.

Posts aimés récemment

J’aime publics du réseau 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.

    Voir le 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.

    Voir le 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.

    Voir le 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.

    Voir le 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

    Voir le post

Connectez-vous pour en voir plus

Comptes bloqués

Sur Bluesky, les blocages sont publics.

Ce compte ne bloque personne.