Legal frameworks for data security are needed now more than ever. Recognizing this long after the journalistic debate giving rise to FERPA and HIPPA, states are creating a range of protection. It is, in my opinion, a sad fact that legislatures are the force driving this in the wake of breaches at Target and the rise of the Silk Road.
Navigating these frameworks and avoiding being placed in front of your local school firing squad sputtering garbage is actually quite simple. Use NIST, follow it well, and add some common sense.
My state of Colorado recently enacted some of the toughest data protection laws in the country. The important pieces for tech companies are:
- Partners need to be verified by the school. Third parties can be vouched for but should also seek verification
- Data can only be used within the confines of the objective stated in the contract
- Companies working with information should de-identify student data for external programs unless working with a trusted party and should only work under the confines of their contract with allowed parties
- Information cannot be used for direct marketing purposes
- A security plan must be presented, in full, and actually deployed
- Use access roles, proper password practices; etc. There are a few companies I can think of that really don’t
- Keep information in audit tables
- A breech will result in a public hearing and intense scrutiny as well as a possible black-listing
Other states, Washington in particular, already have similar laws. Hawaii, a state we are working within through a partner, actually verifies organizations as research partners.
FERPA and HIPPA compliance is really no different:
- Certain data cannot be given out even under FOIA
- Protect against threats using reasonable practices
- Use common sense
Nothing, of course is secure and nothing ever will be. We, as developers, strive to achieve a level of difficulty that dismays.
So, how do you protect data. The government answered that too through NIST:
NIST even maintains a set of acceptable hashes.
As always, remember that security is fluid. Use common sense, patch known breaches, don’t use your database system full of customer information to run your HVAC. You know, the basics.