Best Practices

Integrating File Service Data into Other Systems

Enriching Incidents Generated by Other Systems

Security staff find it difficult to prioritise data loss, system failure, data breach, etc. incidents as they lack knowledge of the sensitivity of the data that was lost, has become unavailable, or was unlawfully accessed.

Incident alert tickets should include relevant information gathered from other systems. In the case of data loss, system failure and data breach incidents, information should be available that exposes the sensitivity, importance and frequency of use of the data in the affected file shares/systems.

An incident is triggered by another system that concerns a file share, SharePoint site, etc.
The creation of the incident runs a set of standard analyses for that repository; identification of PII/PCI that were accessed/modified at the time of the breach, files that may contain password information, etc.
The incident management system can also connect to results of analyses that were previously collected via a recurring schedule.
Links to related dashboards are added to the incident.
Security staff use the additional information to help prioritise and analyse incidents.
Manage the Data Lifcycle
Business Needs Teasers

There are 3 important events in the lifecycle of data; creation, use and deletion. At all other times the data only represents risk.
Read More

Best Practices

Get a better idea of what kind of directives and policies are needed to tackle a specific behavior. Download the Best Practices document

Getting Started

Learn how to ease introduction of UDM with Northern’s parallel approach with this getting started guide.

North America HQ

NORTHERN Parklife, Inc.
301 Edgewater Place, Suite 100
Wakefield, MA 01880

Voice: 781.968.5424
Fax: 781.968.5301


Additional Contact Information


St. Göransgatan 66
112 33 Stockholm

Voice: +46 8 457 50 00

Northern Parklife

©2018 northern parklife

privacy statement 
terms of use