Day 28 — Sprint #3 Retrospective & Building Toward HIPAA Compliance (Part 5)

Sprint #3 Retrospective:

Focus for the Week

Highlights of the Week

💡What I Learned

  • Content development is MUCH easier when solving a problem for a defined audience (and starting on paper). Previously, I would just “design some modules” and it always seemed to take much longer than it should.
  • HIPAA compliance is a scary hill to climb, but it’s also a solved problem, which gives me confidence we can do it.

👍 What Went Well

  • Really happy with content development efforts. I was invigorated to put pen to paper for this challenge and I’m even more excited to test it out.
  • Picked up HIPAA-compliance activities that were started months ago. If we’re to work with hospitals, schools, or anyone else who delivers care and gets reimbursed by insurance, this will be a must.

👎 Opportunities to Improve

  • This particular experiment is taking several weeks longer than the normal one-week sprint cadence. The main reason for that is that we’ve received some early positive feedback and it’s just a really big, unsolved challenge. Still, I need to do better at building rigorous experiments and sticking to our process.
  • Didn’t talk to any new users. It was Christmas, sure, but a little extra planning last week could have allowed some testing at the beginning of this week to get some quick feedback.

⏭️ Next Steps

  • Mostly HIPAA-compliance activities. Goal is to break off most of our planning activities related to HIPAA.
  • Outreach to young adults and families to test new concept.
  • New experiment (?)

The Risk Analysis

1. Organize the Risk Analysis

The baseline tool I’m using is from the NIH (You can access it here).

The risk analysis is organized into 7 sections, some of which I’ve completed already.

  1. SRA Basics
  2. Security Policies — complete
  3. Security & Workforce
  4. Security & Data
  5. Security and the Practice — complete
  6. Security and Business Associates — complete
  7. Contingency Planning — complete

2. Identify Threats & Vulnerabilities

Within each section, there are a number of vulnerabilities which could impact the confidentiality, integrity, or availability of our data in some way. The really nice part about starting with the NIH tool is that most of the initial vulnerabilities and threats are already laid out.

I’ll walk you through an example:

In this case, the vulnerability is that inadequate access controls lead to information disclosure, loss, or theft (i.e., someone gets access to a system they should not have access to and does something bad).

3. Identify Threat Rating

To generate a threat rating, there are 2 components:

  1. Likelihood: How likely is this event to happen?
  2. Impact: If this happened, what would be the consequences?

In this case, the likelihood is Low but the impact if it happened would be Medium, leading us to have a Medium Threat Rating for this threat.

4. Identify Response Actions and Policy Controls

The response action is how we choose to respond to the risk. We have a few choices on our response:

  1. Accept the Risk: We’re comfortable with taking this risk and don’t need to do anything.
  2. Mitigate the Risk: We would like to reduce the likelihood / impact of this risk by applying mitigation controls to this threat.
  3. Avoid the Risk: Do something that will allow us to avoid this risk altogether.
  4. Transfer the Risk: Transfer the risk to someone else (e.g., we do this for our environmental security with AWS).
  5. Share the Risk: Use a 3rd party who shares in the risk (e.g., using Okta for identify management).

For this threat, we have some fairly robust access management policies and procedures for ensuring only the right people have access to the right systems.

5. The End Result

Here’s what this vulnerability looks like with everything put together:

Completing one of our vulnerabilities

And we’re done! Just kidding. This process continues for each vulnerability:threat combo. Here’s what our output looks like for 40 total vulnerabilities.

Our Risk Analysis in Cool Table Form

What’s Next?

Tomorrow I intend to keep chipping away at our HIPAA Compliance work. These little bits of work are making a big dent in our efforts of building in robust data security.

--

--

--

Startup founder surviving in his parent’s basement.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

The Best FREE Cloud Storage for 2022

CONTEST ALERT: WIN 200 $LEXI!

Bazarloader Malware

Server-Side Request Forgery [CWE-918] — The Hacktivists

3 days ‘till PancakeSwap Launch: We open an airdrop program for free PENG

Hosting: A buyer’s guide

{UPDATE} Restaurante de sándwiches Hack Free Resources Generator

{UPDATE} Connect Bubbles 2 Hack Free Resources Generator

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Bob Weishar

Bob Weishar

Startup founder surviving in his parent’s basement.

More from Medium

How Visionary Leader Hassan Jameel Steers With Purpose

How You and Your Team Can Make a Bigger Impact: Get Essential and Multiply

A calculator and a cup of coffee sit side-by-side.

It’s easy to get caught in the big is better CRM database trap.

Why Does Your Startup Need A Founder’s Agreement?