-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create dice-centurion-requirements.md (#318)
- Loading branch information
Showing
1 changed file
with
46 additions
and
0 deletions.
There are no files selected for viewing
46 changes: 46 additions & 0 deletions
46
aws/projects/ois-cloud-storage-security/dice-centurion-requirements.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,46 @@ | ||
| # Malware and Virus Scanning Solution for File Uploads | ||
|
|
||
| ## Use Case Overview | ||
|
|
||
| ### Real-Time Scanning | ||
| - Many surveys require file uploads and immediate feedback to users. | ||
| - A **real-time scanning solution** is essential to process files as they are uploaded. | ||
|
|
||
| ### Backend Scanning | ||
| - For the **Ingest Project** and similar use cases: | ||
| - High volumes of large files are anticipated. | ||
| - Files should be scanned asynchronously using a backend process: | ||
| - Example workflow: **Arrival Bucket → Scan → Permanent Bucket or Quarantine**. | ||
|
|
||
| --- | ||
|
|
||
| ## Requirements | ||
|
|
||
| To meet these needs, we propose implementing an **OIS-approved, enterprise-level virus and malware scanning solution**. The solution should: | ||
| 1. **Support API-based integration** for seamless real-time scanning of incoming files. | ||
| 2. Handle **backend scanning workflows** efficiently within an S3-based architecture. | ||
| 3. Be **scalable and robust** to accommodate varying file sizes and volumes. | ||
| 4. Be a **centrally managed enterprise solution** to ensure consistency and compliance across projects. | ||
|
|
||
| --- | ||
|
|
||
| ## Current Observations | ||
|
|
||
| - **AWS** does not offer a native virus or malware scanning solution. | ||
| - However, **third-party solutions** exist, such as **Cloud Storage Security**, which: | ||
| - Deploy scanning services. | ||
| - Provide API-based functionality. | ||
|
|
||
| - While these tools could meet technical needs, deploying such a solution requires: | ||
| - **Enterprise-level planning.** | ||
| - Approval and alignment with **security and operational standards**. | ||
|
|
||
| --- | ||
|
|
||
| ## Request | ||
|
|
||
| Given the scope and security implications, the Centurion Team requests the **OIS team** to: | ||
| 1. **Evaluate** and **implement** an enterprise-grade malware and virus scanning solution. | ||
| 2. Ensure the solution can serve **multiple projects** across the organization. | ||
|
|
||
| This solution should not be developed or managed by the Centurion Team alone. |