Commit 94631ea2 authored by Dominique Fauteux-Chapleau's avatar Dominique Fauteux-Chapleau Committed by Commit Bot

Add READMEs to deep scanning main directories

Bug: 1109240
Change-Id: I70af6c0371edffbaf4bf108cb332683de4c77bdf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2498880
Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org>
Reviewed-by: default avatarRoger Tawa <rogerta@chromium.org>
Reviewed-by: default avatarDaniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821332}
parent ff38a2c6
This directory contains code used by Chrome Enterprise Connectors. This
includes:
* Code to handle Connector policies.
* Code specific to uploaded content analysis.
* Common utilities used by Connector code.
Code shared with user downloads cloud scanning should be added to
`//chrome/browser/safe_browsing/cloud_content_scanning/` instead.
Code specific to user downloads cloud scanning should be added to
`//chrome/browser/safe_browsing/download_protection/` instead.
This directory includes cloud scanning code that is shared across user uploads
and user downloads scanning features. This includes:
* Chrome Enterprise Connectors that scan content.
* Chrome Advanced Protection Program file download scans.
Code specific to user downloads cloud scanning should be added to
`//chrome/browser/safe_browsing/download_protection/` instead.
Code specific to user uploads cloud scanning or Chrome Enterprise Connectors
should be added to `//chrome/browser/enterprise/connectors/` instead.
This directory includes code that scans downloaded content for security reasons.
This includes:
* Safe Browsing metadata checks.
* Chrome Advanced Protection Program file download scans.
* Chrome Enterprise Connectors file download scans.
Code shared with user uploads cloud scanning should be added to
`//chrome/browser/safe_browsing/cloud_content_scanning/` instead.
Code specific to user uploads cloud scanning or Chrome Enterprise Connectors
should be added to `//chrome/browser/enterprise/connectors/` instead.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment