Event banner
Event details
26 Comments
That concludes this episode of Unpacking Endpoint Management. Thanks for joining! We'll see you again next month in Spooky endpoint dreams: What's keeping you up at night? What are your worst nightmares?
In addition to the questions posted on this page, we also answer questions posted in reply to the event on LinkedIn and Twitter. Here are the questions we answered today:
- Question -- If documents, records, policies, emails are being requested in our Microsoft 365 tenant. What would I need to be able to search and find them? - answered at 08:55.
- From David on LinkedIn -- What about end user privacy? - answered at 13:40.
- Question -- How much of this is actually a surprise to both the companies and end users? - answered at 20:30.
- Question -- How do we stop rogue admins and users from covering their tracks? Destroying data and evidence? - answered at 24:25.
- Question -- What is data spillage, and what is eDiscovery's role in dealing with it? - answered at 30:00.
- From Twitter -- What if I want to pass the buck and delegate responsibilities to other people in my company so I can transfer risk? - answered at 32:45.
- Question -- Has MS considered adding an option to place data rights management controls on data exported from Purview? Time bombs? custody tracking? - answered at 40:40.
- Question -- What is the difference between eDiscovery Standard and eDiscovery Premium? How can organizations streamline the eDiscovery process? - answered at 46:10.
- Question -- What can an IT Pro use as examples to influence a CIO/CTO/CISO to get in front of and protect better against insider risks & potential lawsuits? - answered at 55:00.
- A word of caution. Legal hold is a two-edge sword. Great for preserving data, but the lifecycle of preserved data needs to be monitored so that data no longer needed to be held is released from hold. Otherwis, costly unneeded exposure to data is at risk.
- Love the metadata discovery features. We have one such request in the pipe now.
- The sophistication of EDP, at least as far as SoNH is concerned) demands resources (technicians). This is not an MS issue, but the massive growth of ESI discovery needs. Purview has helped a lot. But success breeds more requests.
Anyone with access to CS can see all queries in CS. Teh queries themselves can contain sensitive case info.
Has MS paired an RBAC secured dedicated srorage solution for exported content to control data spillage? Bhavana answered some of that.
- Chsing down piceons for discovery - had to do that. They do die usually before they can be used as evidence
- State of New Hampshire is very close to delegating access to counsel within state agencies to perform their own case-related searches and date exports with data access controls. It is complex to do and requires training. It aboslutely makes sense withing the EDRM. We do tell them not to use Content Search given the more lax RBAC controls. IT controls case creations, hold configurations, and data access within Discovery Standard.
- Has MS considered adding an option to place data rights management controls on data exported from Purview? Time bombs? custody tracking?
- Heather_Poulsen
Community Manager
We'd love to know more about your desired capabilities and use cases. If you can share more here, please do. If not, please feel free to send a private message to our panel speakers here in the Tech Community.
We have a good dsicovery and data preservation solution (MS EDS), but have not coupled it with a centralized storage repository where we can better manage the lifecycle of exported data. Some of that is on us and there are storage solutions both on-prem and in the cloud where we can do that, some of which we can apply sensitivity labels and DLP to. In the Universe of Purview, does MS have it on their roadmap to provide an end-to-end solutiion for discovery, preservation, AND storage for legal data?
We're halfway through! Keep those questions flowing, and share information about use cases and scenarios you need to support. Post away in the Comments.
