Sopuli
  • Communities
  • Create Post
  • Create Community
  • heart
    Support Lemmy
  • search
    Search
  • Login
  • Sign Up
thebeesknees@feddit.nl to cybersecurity@infosec.pubEnglish · 2 years ago

Compromised Microsoft Key: More Impactful Than We Thought | Wiz Blog

www.wiz.io

external-link
message-square
3
link
fedilink
  • cross-posted to:
  • tech@kbin.social
  • sysadmin@lemmy.world
  • hackernews@derp.foo
  • secops@lemmy.world
  • sysadmin@lemmy.ml
13
external-link

Compromised Microsoft Key: More Impactful Than We Thought | Wiz Blog

www.wiz.io

thebeesknees@feddit.nl to cybersecurity@infosec.pubEnglish · 2 years ago
message-square
3
link
fedilink
  • cross-posted to:
  • tech@kbin.social
  • sysadmin@lemmy.world
  • hackernews@derp.foo
  • secops@lemmy.world
  • sysadmin@lemmy.ml
Our investigation of the security incident disclosed by Microsoft and CISA and attributed to Chinese threat actor Storm-0558, found that this incident seems to have a broader scope than originally assumed. Organizations using Microsoft and Azure services should take steps to assess potential impact.
alert-triangle
You must log in or register to comment.
  • br3ad@infosec.pub
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 years ago

    Fantastic writeup. I wonder, how does a threat actor get access to a signing key like this? There was no mention of how the key got leaked in the first place.

    • helpmeplease@infosec.pub
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 years ago

      Below is a more detailed report about the IOCs, but indeed, they don’t seem to want to say anything about the original source of the key leak.

      https://www.microsoft.com/en-us/security/blog/2023/07/14/analysis-of-storm-0558-techniques-for-unauthorized-email-access/

    • thebeesknees@infosec.pub
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 years ago

      Yes, that part is still undisclosed by Microsoft. It is mentioned in the article as well:

      We will continue to closely monitor this incident and provide updates; this is still an ongoing investigation and there are many unanswered questions (how did the threat actor acquire the key? When exactly did it happen? Were other keys compromised as well?).

    • helpmeplease@infosec.pub
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 years ago

      deleted by creator

cybersecurity@infosec.pub

cybersecurity@infosec.pub

Subscribe from Remote Instance

Create a post
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !cybersecurity@infosec.pub

An umbrella community for all things cybersecurity / infosec. News, research, questions, are all welcome!

Community Rules

  • Be kind
  • Limit promotional activities
  • Non-cybersecurity posts should be redirected to other communities within infosec.pub.

Enjoy!

Visibility: Public
globe

This community can be federated to other instances and be posted/commented in by their users.

  • 14 users / day
  • 281 users / week
  • 640 users / month
  • 1.79K users / 6 months
  • 42 local subscribers
  • 4.38K subscribers
  • 701 Posts
  • 1.61K Comments
  • Modlog
  • mods:
  • shellsharks@infosec.pub
  • tweedge@infosec.pub
    cake
  • BE: 0.19.11
  • Modlog
  • Legal
  • Instances
  • Docs
  • Code
  • join-lemmy.org