digitalcourage.social

Dissent Doe :cupofcoffee:<a href="https://infosec.exchange/@amvinfe" class="u-url mention" rel="nofollow noopener" target="_blank">@amvinfe</a> <a href="https://noc.social/@AAKL" class="u-url mention" rel="nofollow noopener" target="_blank">@AAKL</a> <a href="https://infosec.exchange/@brett" class="u-url mention" rel="nofollow noopener" target="_blank">@brett</a> <a href="https://ioc.exchange/@jgreig" class="u-url mention" rel="nofollow noopener" target="_blank">@jgreig</a> It seems pretty clear from what BianLian has posted that there were TWO unrelated attacks, but Akumin has only disclosed the first attack -- even though it has issued updates since the time of the second attack.That said: if the second attack was in November, as it allegedly was, then Akumin is still within a 60-day window from discovery to when it must notify HHS and affected patients. But if an entity issues a press release or update that discloses one data breach but is silent on the fact that there was a second breach, too, resulting in the theft of patient data, is that a deceptive or unfair act under Section 5 of the FTC Act?<a href="https://infosec.exchange/tags/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#transparency</a> <a href="https://infosec.exchange/tags/incidentreponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#incidentreponse</a> <a href="https://infosec.exchange/tags/extortion" class="mention hashtag" rel="nofollow noopener" target="_blank">#extortion</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#databreach</a>

Dissent Doe :cupofcoffee:<a href="https://infosec.exchange/@brett" class="u-url mention" rel="nofollow noopener" target="_blank">@brett</a> I don't know if I missed something or forgot anything, but have we seen any real statement from the hospitals or TransForm about whether they had recent and usable backups?<a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/HealthSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#HealthSec</a> <a href="https://infosec.exchange/tags/backups" class="mention hashtag" rel="nofollow noopener" target="_blank">#backups</a> <a href="https://infosec.exchange/tags/restoration" class="mention hashtag" rel="nofollow noopener" target="_blank">#restoration</a> <a href="https://infosec.exchange/tags/incidentreponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#incidentreponse</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener" target="_blank">#ransomware</a>

HiSolutionsZwei von drei deutschen Unternehmen wurden im Jahr 2022 lt. eines aktuellen Reports Opfer einer Cyberattacke. Im Creditreform <a href="https://infosec.exchange/tags/Podcast" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podcast</a> spricht <a href="https://infosec.exchange/@LisaLobmeyer" class="u-url mention" rel="nofollow noopener" target="_blank">@LisaLobmeyer</a> über <a href="https://infosec.exchange/tags/Ransomware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ransomware</a>, <a href="https://infosec.exchange/tags/IT_Sicherheit" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT_Sicherheit</a> und präventive Maßnahmen für Unternehmen, um im Angriffsfall souverän reagieren zu können.Jetzt hören ▶️ <a href="https://www.creditreform.de/aktuelles-wissen/podcast/podcast-details/show/it-sicherheit-souveraen-auf-angriffe-reagieren" rel="nofollow noopener" translate="no" target="_blank">https://www.creditreform.de/aktuelles-wissen/podcast/podcast-details/show/it-sicherheit-souveraen-auf-angriffe-reagieren</a><a href="https://infosec.exchange/tags/IncidentReponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#IncidentReponse</a> <a href="https://infosec.exchange/tags/Cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cybersecurity</a> <a href="https://infosec.exchange/tags/BlueTeam" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlueTeam</a>

Recent searches

Search options

Administered by:

Server stats:

#incidentreponse