Cybersecurity continues to be top of mind in new ways that we might not have considered during “normal” times. One area that needed our attention then and now is vendor management. Especially with the mad dash over the summer to get many districts ready for at least some remote learning, there are a lot of new third-party vendors on the scene.
Pre-COVID, third-party vendors for schools and districts meant everything from transportation systems and student information platforms to applications like PowerSchool, Quizlet, and Google Classroom. Post-COVID, the term references all of that–plus things like COVID tracking and tracing programs.
Related content: 3 ways to improve online learning security
Regardless of whether we are talking pre- or post-pandemic, third-party vendor risk is a serious thing. Ponemon Institute found that in the United States, 61 percent of data breaches were caused by third parties and vendors.
Are you wondering if you should get rid of third-party vendors? There’s no need to take such a dramatic step, but you should plan to get more focused on knowing what third-party vendors bring to the table when working with your school or district.
Let the vetting begin
Vetting third-party vendors is like asking a teenager if they cleaned their room. As long as you don’t look under the bed or in the closet, everything looks good. The problem is, when you’re running a school, you have to really dig into those dark places no one wants to look.
It doesn’t matter if you are hiring a new vendor or examining one the school has worked with for 30 years–the best way to get a baseline on a vendor is to run a risk assessment on them. Just like you assess physical risks to your school, best practice dictates that you apply the same rigor to the companies you work with and that have access to student or parent data.
While it won’t help you make sure the vendor contract is written fairly, a well-executed vendor risk assessment will help you understand how every vendor handle security and privacy. It will also uncover those vendors that pass all responsibility off to the school or district, and, conversely, those that will act as true partners that want to work with you if something goes awry.
4 key areas to focus your efforts
Once you’ve done a complete risk assessment and know who brings what to the table, there are four critical areas you need to focus your attention on to help minimize vendor risk:
1. The Contract: Your district is not going to cut a check to any vendor without first having a contract in place. But, when it comes to data privacy and breach specifics, what’s in that contract? Who owns student and parent data? If something does go wrong, what responsibilities does the district have vs. the vendor?
Questions such as these are critical to understand and agree upon before moving forward. State privacy laws vary, and you need to understand yours because they define what the school or district’s obligation looks like. For instance, in some states, if a data breach occurs, the party that notifies individuals of the breach is financially responsible for things like annual credit monitoring for the victims. This type of financial outlay can get very expensive for a district very quickly, so it is critical that you denote in your contract what obligations your vendor has to your district and school should a data violation occur.
2. Disaster Recovery: All of us have had the internet go out during a critical task. The same will happen at some point with your vendors. There is nothing wrong with asking – and in fact, you should ask – what happens if your service/product goes out? What’s the alternative? Your district or school is depending on your vendors, so work with vendors to create a responsible expectation for when services will be restored.
3. Data Destruction: Taking a page from Europe’s book, many U.S. states have adopted data privacy laws much like GDPR. California, Delaware, Illinois, Louisiana, Maine, and Texas are among those recognized as having the toughest data privacy laws in the country, and most have requirements stipulating that if data needs to be destroyed, it be destroyed everywhere – including with vendors and in backups. Work into your contracts that if data needs to be destroyed, you get it back from the vendor and do it yourself, or, if the vendor destroys it, they do so pursuant to NIST Special Publication 800- 88 guidelines. Either way, make sure there is proof that the data has been destroyed properly.
4. Vendor Privacy Policy: It’s an absolute *must* that your vendors show they are compliant with both the Children’s Online Privacy Protect Rule (COPPA) and the Children’s Internet Protection Act (CIPA). COPPA prevents vendors from collecting personal information from children under the age of 13, while CIPA blocks or filters internet content that is obscene or harmful to children. If a vendor can’t prove they are COPPA and CIPA compliant, find a different vendor. Period.
Third-party vendors help your schools offer fantastic services to your students. However, the fact that third-party vendor risk is one of the fastest-growing cybersecurity threats in the industry means that vetting your partners is more important than ever. You want partners that are in the arena with you, not just collecting a check. First and foremost, you have to assess the risk a vendor brings to your school or district. Then you have to get into the weeds to understand how they handle data, service delays and privacy. If a vendor seems too in it for themselves and isn’t showing an interest in making you successful or keeping your students secure, keep looking.
- 3 ways to avoid summer learning loss - April 19, 2024
- High school students say AI will change the workforce - April 18, 2024
- Motivating students using the Self-Determination Theory - April 17, 2024
