DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

DocuTrac medical software is a breach risk, warns Rapid7

Posted on March 15, 2018 by Dissent

Warwick Ashford reports on what seems to me to be yet another case of hard-coded credentials creating a critical vulnerability in protecting patient data, and I, of course, have questions. Ashford reports:

The QuicDoc & Office Therapy suite of software produced by DocuTrac contains security vulnerabilities that could allow attackers to gain control of patient data, warns security firm Rapid7.

[…]

According to Rapid7, the software contains a number of static accounts that are not disclosed to the end-user, and are identical across all installations of the medical records software.

Read more on ComputerWeekly.  I looked to see what DocuTrac claimed about HIPAA compliance and found the following on their site:

Our practice management and clinical documentation software for behavioral health providers has HIPAA compliant features for the security of protected health information (PHI). DocuTrac’s HIPAA features whether Cloud or Client-Server based include secure access, audit log tracking for internal audits, and a disclosure of protected information log to record and track all PHI disclosures. Our practice management software uses HIPAA compliant files for electronic claims and contains HIPAA compliant procedure and diagnosis codes.

We ensure all our electronic medical records software, electronic health record software, medical billing software, practice management software, and e-prescribing software are HIPAA compliant to assist healthcare organizations in protecting their sensitive data.

But is it really HIPAA-compliant if there are hard-coded credentials?  Or are there other safeguards that they incorporate that somehow minimize the concern over hard-coded credentials? I’d love to have an expert explain that to me.

As to the time to disclosure, Ashford reports:

Although DocuTrac was alerted to the vulnerabilities on 9 January 2018 and two subsequent communications via telephone and email, no software update had been issued by 14 March, when Rapid7 went public with the vulnerabilities.

Was QuicDoc given enough time to remedy the problem before Rapid7 went public? How long should they have been given to address the issue? Regardless of whether you think that the issue never should have occurred, if it did occur, what would be a reasonable amount of time to address it before it was disclosed?

Category: Commentaries and AnalysesHealth DataU.S.

Post navigation

← Nampa School District investigating cyber security breach
OAIC received 31 notifications in the first three weeks of data breach scheme →

2 thoughts on “DocuTrac medical software is a breach risk, warns Rapid7”

  1. kilgore says:
    March 16, 2018 at 8:40 pm

    I think 90 days notification before disclosure is a good starting point, which should be clearly communicated up front. If it can be shown a true good faith effort is being made to address the vulnerability, perhaps adjustments can be made to the timeline.

    It’s hard to tell here if this was reasonable public disclosure as there’s no mention of DocuTrac’s efforts to address the issues. No patch was released in 60 days, but we don’t know if they were close to having one – or if they simply blew off Rapid7’s communications.

    1. Dissent says:
      March 16, 2018 at 9:10 pm

      So suppose the government had the ability (and had exercised it) to take enforcement action and DocuTrac goes to settle the government’s complaint. In how many days would they agree to patch, I wonder? What would the government say is reasonable? Sixty days? Ninety? Sometime before the end of my life?

Comments are closed.

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Nova Scotia Power hit by cyberattack, critical infrastructure targeted, no outages reported
  • Georgia hospital defeats data-tracking lawsuit
  • 60K BTC Wallets Tied to LockBit Ransomware Gang Leaked
  • UK: Legal Aid Agency hit by cyber security incident
  • Public notice for individuals affected by an information security breach in the Social Services, Health Care and Rescue Services Division of Helsinki
  • PowerSchool paid a hacker’s extortion demand, but now school district clients are being extorted anyway (3)
  • Defending Against UNC3944: Cybercrime Hardening Guidance from the Frontlines
  • Call for Public Input: Essential Cybersecurity Protections for K-12 Schools (2025-26 SY)
  • Cyberattack puts healthcare on hold for hundreds in St. Louis metro
  • Europol: DDoS-for-hire empire brought down: Poland arrests 4 administrators, US seizes 9 domains

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Apple Siri Eavesdropping Payout Deadline Confirmed—How To Make A Claim
  • Privacy matters to Canadians – Privacy Commissioner of Canada marks Privacy Awareness Week with release of latest survey results
  • Missouri Clinic Must Give State AG Minor Trans Care Information
  • Georgia hospital defeats data-tracking lawsuit
  • No Postal Service Data Sharing to Deport Immigrants
  • DOGE aims to pool federal data, putting personal information at risk
  • Privacy concerns swirl around HHS plan to build Medicare, Medicaid database on autism

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.