registers that the user attempted to move a
file from the endpoint to the peripheral device and evaluates your Endpoint
DLP policy rules.
No Policy Rule Match—If there is no Endpoint DLP policy
rule match identified, then the agent allows the peripheral
device to connect and the endpoint has full read and write
access privileges to the peripheral device.
Peripheral Control Policy Rule—If you created a peripheral
control policy rule to control access, then the agent executes
the allow or block action that you configured in the policy
rule.
For example, if the Endpoint DLP policy rule blocks the
connection to the peripheral device, then the agent revokes
write privileges to the peripheral device. In this case, the
endpoint can't upload files to the peripheral device.
Alternatively, if the Endpoint DLP policy rule allows the
connection to the peripheral device, then the agent grants the
endpoint write access privileges to the peripheral device. In
this case, the endpoint can upload files to the peripheral
device.
Data in Motion Policy Rule—The agent allows the connection
to the peripheral device. When the Prisma Access Agent
detects file movement from the endpoint to a peripheral device,
the file is forwarded to Enterprise DLP for inspection and
to render a verdict. The agent also forwards important file
metadata, such as the fileSHA,
which Enterprise DLP uses to identify each forwarded file.
Enterprise DLP then sends the verdict to the Prisma Access Agent and, if sensitive data is detected,
the agent takes the Endpoint DLP policy rule action. If Enterprise DLP detects that it's a file that has already
been inspected based on the
fileSHA, then Enterprise DLP
returns the existing verdict to the agent. Enterprise DLP
does not inspect the same file twice.