Here’s another great post from Jim Gill of Hanzo on considerations with various ESI sources. This post analyzes SaaS API limitations for eDiscovery and Compliance!
The article Analysis of SaaS API Limitations for Ediscovery and Compliance (available here), Jim discusses how Application Programming Interfaces (APIs) can give users the ability to use 3rd party solutions to preserve, collect, and even cull data housed in a SaaS application for eDiscovery and governance; however, functionality is still limited to what the API is built to communicate.
Even if an application has an API available, its design is often focused on the modification of objects and data rather than the creation of a consumable, universal format expected by legal and compliance teams.
It may also only capture text-based information and may lack some of the visual and dynamic features of the original interface, which can be quite important when it comes to understanding and contextualizing the data.
The best part of the article is when Jim discusses some of the general challenges one might face when trying to collect data from complex SaaS applications, specifically applications for CRM (Customer Relationship Management), HRIS (Human Resources Information System), Project Management and Ticketing. He gives examples of each and discusses some SaaS API limitations and challenges for each. These are terrific examples that illustrate just how complex linking to these solutions is.
So, what are some SaaS API limitations for eDiscovery and Compliance? You’ll have to read his blog post here to find out! It’s just one more click!
Webinar alert! Hanzo is conducting its next installment in its Luminary Series (How Recent Regulatory Rulings Are Shaping Compliance) on July 28th at 1pm ET! This installment will feature a discussion with former United States Magistrate Judge for the District of New Jersey, Ron Hedges, who is a Senior Counsel with Dentons.
In this Luminary Chat with Jim and Judge Hedges, you’ll learn:
- How settlement agreements entered by the Federal Trade Commission have shaped compliance policy
- Two approaches to cybersecurity best practices
- Which standards are deemed reasonable under the New York Shield Act
- Compliance Guidelines of the US Department of Justice
Last week, I pointed you to the registration page, but this week, Jim has written a blog post here about the webinar to set the stage for it. Check it out, then register!
So, what do you think? Have you experienced SaaS API limitations in eDiscovery or Compliance? Please share any comments you might have or if you’d like to know more about a particular topic.
Disclosure: Hanzo is an Educational Partner and sponsor of eDiscovery Today
Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by my employer, my partners or my clients. eDiscovery Today is made available solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Today should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.