Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 9 submissions in the queue.
posted by hubie on Sunday September 06, @12:21PM   Printer-friendly

McKesson admits breach as ShinyHunters demands $55.2M:

Two major healthcare businesses, Boston Scientific and McKesson, disclosed more details over the weekend about separate cyberattacks that disrupted global operations and resulted in stolen patient data, respectively.

Medical-device maker Boston Scientific, whose IT systems were hacked by unknown intruders last week, said the cyberattack remains ongoing. It also noted that pacemakers and other heart devices implanted after the August 25 breach cannot provide remote monitoring and data transmission as intended.

"New remote monitoring communicators cannot be activated, thus available device data will NOT be transmitted to remote patient management systems until the communicator can be activated," the medtech firm said in a late Friday update. 

This applies to all new cardiac rhythm management implants other than insertable cardiac monitors (ICM). 

ICM devices must be activated using the Boston Scientific Clinic Assistant app to ensure the device correctly records patients' heart rhythms, the company added. 

Because of the cyberattack, "new ICMs are unable to pair to the patient remote monitoring mobile phone, therefore available episode data recorded by the ICM will NOT be transmitted to the remote monitoring system until the ICM can be paired to the patient mobile app," according to the update. 

The devices will still record any episodes, and patients can transmit these to the remote monitoring system by in-person transmission via the Clinic Assistant app. This is done by selecting the "interrogate" button, according to the company.

Once its IT systems are back up and running, and the heart devices can pair with home monitoring equipment, they will again transmit recorded data to the remote systems.

[...] Meanwhile, in another cybersecurity incident that has been very publicly claimed by the criminal perpetrator: pharmaceutical and medical supply giant McKesson over the weekend confirmed an intrusion after ShinyHunters on Friday told The Register it broke into the company's Snowflake and Salesforce instances and stole millions of patients' data.

"Based on our investigation thus far, including assessments by leading cybersecurity industry experts supporting our response, we've confirmed that the unauthorized access to certain third-party applications and the exfiltration of certain data was associated with a subset of customers within our Oncology & Multispecialty and Medical-Surgical business units," Francisco Fraga, McKesson executive VP, chief information officer and chief technology officer, said in a Saturday statement. 

[...] The McKesson records, according to the ShinyHunters spokesperson, include patients' full names, home and email addresses, phone numbers, dates of birth, Social Security numbers, appointment dates and notes, and sensitive illness details including cancer locations on people's bodies. The group also claims to have swiped emails containing private information from doctors to patients.

The spokesperson told us they accessed the company's Snowflake and Salesforce instances by voice phishing "multiple employees." This is a tried-and-true method popularized by the data-theft-and-extortion gang, which has victimized other medical providers in recent months. These include pacemaker manufacturer Medtronic in April, and cancer diagnostics business Exact Sciences in July.


Original Submission

 
This discussion was created by hubie (1068) for logged-in users only, but now has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by Bentonite on Sunday September 06, @02:00PM (3 children)

    by Bentonite (56146) on Sunday September 06, @02:00PM (#1453127)

    Security Through Obscurity is not real security.

    Obscurity is the exact opposite of security.

    Security consists of every detail of the system being available for public scrutiny, so the security flaws end up getting found and fixed.

    If any part is obscure, then anyone who bothers to work out the obscurity can exploit the unfixed security flaws.

    (An encryption key etc should not be kept obscure, hidden under a doormat - it should be kept secret instead - an encryption key that can be reset as needed, is the only thing that can be reliably kept secret anyway).

    Their idea of a strong password is the old "capital letter, lowercase letter, number, Special Character, and length at least 8." (While that's not totally wrong

    That is a totally wrong password rule - that causes 99% of people to either go for; Password1! or a weak password that is hard for humans to remember, but easy for computers to guess.

    The issue is compounded with regular forced password changes - most humans can't remember a password that is changed every month, unless that password is; Password1! and is changed to Password2!.

    The only rule should be 8+ characters, which would allow an actually secure password to be used, for example 6 random words, although even a measly 3 words (provided the dictionary is substantially larger than the diceware set), is likely to have more entropy than what humans can come up, that can be remembered, according to those rules.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 4, Insightful) by JoeMerchant on Sunday September 06, @02:52PM

    by JoeMerchant (3937) on Sunday September 06, @02:52PM (#1453131) Journal

    >Obscurity is the exact opposite of security.

    In extremis, this is true. Obscurity kicks the can down the road, makes people comfortable without security. Sometimes it "works" effectively forever:

    During the Viking Age (c. 793–1066 CE), Norse masters frequently used encrypted runes called lönnrunor (secret runes). While many Viking ciphers (like the famous Rök Runestone) have been solved using basic substitution logic, several remain entirely unbroken.

    The Cipher Method: The Vikings typically used a grid-coordinate system based on the division of the runic alphabet (futhark) into three distinct groups. By drawing a vertical line and counting the branches on the left and right, they could hide letters.

    Unbroken Examples: Certain fragments, such as the cryptographic inscriptions on the Sigtuna box or isolated sections of the Bergen runic inscriptions, feature highly complex, non-standard variants of these coordinate ciphers that have stymied modern computational linguistics and runologists.

    Were the runic codes truly secure? Most of them were broken, one might say the keys were more obscure than secure - but some methods apparently were obscure enough...

    The problem with true security is that it has unavoidable costs and complications which are very real, immediate, and at many times outweigh the value of the secrets being protected. Couple that with the lower costs and still somewhat practical effectiveness of obscurity methods and you hit the question: how long do you need this secret to remain secret? Will an obscurity method serve that need?

    --
    🌻🌻🌻🌻✌️ [google.com]
  • (Score: 2) by Dr Spin on Monday September 07, @08:49AM (1 child)

    by Dr Spin (5239) on Monday September 07, @08:49AM (#1453240)

    I have been a computer user since about 1973. I have 25 pages of passwords and am too old to remember any of them. They are kept in an encrypted file, with a backup on tape.

    I have two tower PCs, a Mac Mini, two Android tablets and two phones. On some of them, there is a password manager that that mostly works.

    Yes, it is a total bloody nuisance.

    Passwords need to be fixed replaced NOW. Surely there is at least one clever person in the world!

    My best guess is that all hardware should be compelled by law to have an integral RFID reader that can read my (previous) bus pass or one of my (out of date) debit cards that I can mark inactive and discard when I want to change my ID. And bleep like crazy if the ID is reported compromised.

    Obviously, I should be able to register more than one card with each device, so as to have a fallback if the active card is compromised or lost.

    --

    However, if my ID here is compromised, I might not want my CURRENT back card blocked. I am not saying that the service provider should have say in which card is used,
    although I would expect banks to insist. I think Soylent, and others like it should have NO SAY at all as to which cards I use. I should be free to register whatever card I like (possibly with my browser) and change it whenever I like - preferably without their knowing. As in, the browser should have a way to negotiate security, like HTTPS, that ensures, in a way not compromisable by the user, that depends on the ID read from the card.

    --
    Warning: Opening your mouth may invalidate your brain!
    • (Score: 2) by Bentonite on Monday September 07, @10:06AM

      by Bentonite (56146) on Monday September 07, @10:06AM (#1453247)

      that all hardware should be compelled by law to have an integral RFID reader

      No, RFID readers must not by required by law - a computer must not be required to have any sort of specific input device, as if such requirement exists, then that *will* be used for evil.

      A requirement to bleep when an RFID tag is compromised, adds a surveillance requirement and also would likely end up with a bunch of the card-passwords being transmitted over HTTP to some ??? server (as that's what the typical proprietary software developer will do to implement the checking part of the requirement).

      There are already plenty of hardware authentication devices that communicate via usb or bluetooth, but almost all of them are backdoored to hell with proprietary software.

      that can read my (previous) bus pass or one of my (out of date) debit cards that I can mark inactive and discard when I want to change my ID.

      Debit cards and bus cards use a bunch of different versions of RFID or NFC depending on the cards.

      NFC is encumbered by patents until at least 2030 (patent expiry doesn't even save RFID, as what companies do is make a slight mathematical change to RFID and then patent that).

      While it wouldn't be technologically infeasible to design a reader that can read most RFID and NFC tags, it wouldn't be commercially feasible to get such reader manufactured, due to the queue of rent seekers that will show up.

      Passwords need to be fixed replaced NOW. Surely there is at least one clever person in the world!

      Anyone with the slightest bit of intelligence has realized that passwords as a concept are not broken and all so-called "replacements" to passwords are always insecure, without fail.

      To use such cards as a password is a terrible idea as;
      - The stored value on the card is likely to be of low entropy and easy to bruteforce.
      - The producer of the card is storing the card value on some insecure database somewhere.
      - Someone walking past you with a RFID/NFC antenna hidden in a backpack, will likely be able to scan the cards and therefore get your password (not that uncommon with credit cards - which is why RFID-blocking wallets exist - but the effectiveness of an ungrounded Faraday cage isn't great).

      If you really want, you could implement such scheme yourself as a PAM module on GNU/Linux - on tapping the card, the user account will log in and you can also use it to unlock a password manager that uses PAM - but that would be less secure that just choosing a single decent password for PAM.

      For forum sites like soylent, you may as well let a web browser store a random password for you, as it really doesn't matter if an attacker manages to post with your account does it?