サポートと今すぐチャット
サポートとのチャット

On Demand Global Settings Current - Security Guide

Separation of Customer Data

For Azure Data Explorer, each organization is contained within a separate database ensuring no mixture of data.

For Azure Storage, a combination of techniques is employed. In Azure Blob Storage the primary technique employed is to keep each organization in a separate container. For other Azure Storage services and when Azure Blob Storage data cannot be separated using containers, the architecture will employ careful use of the organization identifier to ensure data is kept separate.

For Azure Cosmos DB, the architecture will employ careful use of the organization identifier to ensure data is kept separate.

Network Communications

FIPS 140-2 Compliance

On Demand Core cryptographic usage is based on Azure and AWS FIPS 140-2 compliant cryptographic functions.

More information on approved crypto functions is available at NIST FIPS 140-2 https://csrc.nist.gov/publications/detail/fips/140/2/final

 

 

SDLC and SDL

The On Demand team follows a strict Quality Assurance cycle.

In addition, the On Demand Development team follows a managed Security Development Lifecycle (SDL) which includes:

On Demand developers go through the same set of hiring processes and background checks as other Quest employees.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択