Organisational Importance of DLP (Data Loss Prevention)

Organisational Importance of DLP (Data Loss Prevention)

Organizational Importance of DLP (Data Loss Prevention)

Data loss prevention policies, often known as DLP policies, are the foundations of safeguarding your business’s most valuable asset (Company confidential data). Low code technology applications like Power Apps, Power Automate, and Power BI use data. 

Developers used connectors to use these data sources. There are over 100 connectors available by Microsoft; they all provide access to a wide range of data sources. Using these connectors, not only do they get data, but they can also manipulate it. An organization must ensure some policy so their data can be secure; we can use the DLP policy. 

For example, if a company has some confidential data, but no DLP policy is applied, any of the developers, with the use of a connector available, send that data to his mail ID or put it directly on Social platforms like Twitter or Facebook. To prevent this, every company must ensure some policies.

DLP policy can be applied to the tenant level or environment level.

Steps to deploy DLP Policies for Default Environment

Pre-Requisites:

    1. You need to be an Environment Admin or a Power Platform Admin to be able to establish or amend DLP policies.

Microsoft Connectors types:

Business: One or more connectors from the business group may be used by a specific Power App or Power Automate resource. Any non-business connectivity cannot be used by this resource that employs a business connector

Non-business: One or more connectors from a non-business category may be used by a specific Power App or Power Automate resource. Any business connectivity cannot be used by this resource that already uses a non-business connector.

Blocked: A connector from a blocked group cannot be used by a Power App or Power Automate resource. It is possible to ban both ordinary and premium third-party connectors and all premium connectors owned by Microsoft. It is impossible to block any standard connectors or Common Data Service connectors controlled by Microsoft.

Default Environment DLP Policy

Steps to Create a Default DLP Policy:

    1. Log in to the Power Platform Admin center.
    1. Click on Data policies in the left-hand navigation menu. If policies have yet to be created, the following screen will appear. 

 

    1. Click on data policies following screen appears:

 

    1. Specify the Policy name as “Default_Environment_DLP_Policy” and click Next.

 

    1. In the next screen (Connectors), click on the gear icon with the Set default group.

Once you click on “Set default group” below, the popup will open.

Select Non-business and click on Apply.

This will ensure that any new connectors added will be in the Non-Business group by default and can be moved to business or blocked as per the company policy as deemed necessary.

    1. In the connectors screen, enter “Adobe Sign” in the Search connectors search box. Once the searched connector is found, click on the details button “…” and select “Block.”

 OR

You can select multiple connectors, click the details button “…” and select “Block.”

    1. This will move the selected connectors to the Blocked Connectors group and will not be available to makers.

 

    1.   Similarly, as recommended in the List of DLP Policies Connector document, the following connectors need to be blocked.

    1. In the connectors screen, enter “Dynamics 365 Customer Voice” in the Search connectors search box. Once the searched connector is found, click on the details button “…” and select “Move to Business.”

OR

You can select multiple connectors, click the details button “…” and then select “Move to Business.”

    1. This will move the selected connectors to the Business Connectors group and will be available to makers.

Below is the recommended list of connectors that could be added for a start. The policy could be updated later to add or remove any connectors from the business as deemed necessary.

    1. Click Next.

Custom connectors may be utilised with both Business and Non-Business connector groupings if an Ignore * rule is in place and there is no specific rule for the custom connectors.

    1. Click “Next.”
    1. Select multiple environments in this screen and click Next.

    1. Select the BugendaiTech (default) environment in which you want to apply.
    2. Click on “Add to Policy.”


    1. Click on “Next.”


    1. Review the details and click on “Create Policy.”

 

Once the policy gets created below screen will be displayed.

Edit Existing DLP Policies

A policy can be edited by selecting the policy and clicking the action we need to perform.

 

  1. Select Policy which you want to edit and click on “Edit Policy.”
  1. Click “Next.”

  1. If you want to add connectors, Select all connectors which you want to add and click on “…” and then click on “Move to Business.” 

If you want to remove the connectors from business, then first click on “Business” tab; after that, Select all connectors which you want to remove and click on “…” and later click on “Move to Non-business.” 

If you want to remove the connectors from the business, then first click on the “Business” tab; Select all connectors which you want to remove and click on “…” and then click on “Block .”Selected Connectors will be moved to the block.


  1. Click on “Next.”

Custom connectors may be used with both Business and Non-Business connector groupings if no explicit regulation specifically prohibits their use.

 

  1. Click “Next”.
  2. Select multiple environments in this screen and click Next.

  1. Click “Next”.


  1. Review the details and Click on “Update Policy”.


Once the policy is updated, It will show the below screen with the success message “The policy was successfully updated.”


Impact of DLP Policies on PowerApps/Power Automate

  • Design-time impact on apps and flows

    1. PowerApps

An appropriate error message about any DLP policy conflicts will be displayed to users who create or change a resource that is subject to the DLP policy.

For instance, when Power Apps creators employ connectors in an app that is inappropriate together or is prohibited by DLP standards, they will notice the following message. The app can’t add the connection.


    1. Power Automate

The same is true for Power Automate makers who attempt to save a flow using connectors that shouldn’t be used together or that have been forbidden by DLP policies. They will encounter the following error.

Although it will be suspended, the flow itself will be saved.

Runtime impact on apps and flows

    • PowerApps

When Power Apps creators and users attempt to open an app with connectors that do not belong together or have been forbidden by DLP regulations, they will see the following error.


    • Power Automate

Power Automate makers and users won’t be able to start a flow that uses connectors that don’t belong together or have been blocked by DLP policies. 

The flow is marked as Suspended by a background system procedure, and it will not be processed until the maker addresses the DLP policy violation.

Conclusion:

Finally, certain DLP solutions may also deliver notifications, enable encryption, and isolate data when a breach or other security incident is detected. By spotting weak points and unusual activities during routine networking monitoring, the DLP system helps hasten incident response.

Summary
Article Name
Organisational Importance of DLP (Data Loss Prevention)
Description
The cornerstones of protecting the company's most priceless asset (Company confidential data) are data loss prevention policies or DLP policies.
Author
Publisher Name
BugendaiTech Pvt Ltd
Publisher Logo
Spread the updates

Related Posts

Leave a reply



Notice: Undefined index: position_on_screen in /home/tl2jq5v7asif/public_html/wp-content/plugins/mystickyelements/mystickyelements-front.php on line 203