Laserfiche WebLink
SOLICITATION # CH16012 <br />VMWare AirWatch <br />AirWatch uses industry recognized tools and follow best practices to deploy, configure, and <br />maintain server images. We do not apply customer -supplied templates and do not share templates <br />with customers. <br />Our Information Security team identifies applicable security standards and the AirWatch Server <br />Team creates a secure baseline image for deployment throughout the SaaS environment. <br />Due to FOIA restrictions, additional information regarding capacity planning and image <br />creation/safeguarding cannot be disclosed at this time. <br />FireE e <br />This is not applicable as each of FireE e's offerings are classified as SaaS. <br />8.17.2 Provide tool sets at minimum for: <br />1. Deploying new servers (determining configuration for both stand alone or part of an existing <br />server farm, etc.) <br />CA <br />APM <br />New servers are predefined by the CA SaaS Ops toolchain, and automated using <br />AWS tooling to be able to bring up/down servers on demand <br />MAA <br />Same as above. <br />CA Agile <br />We utilize configuration management tools to ensure consistent configuration across <br />our servers. <br />ASM <br />Same as above. <br />Google <br />1. This is not applicable to Google. Capacity planning and server deployment is fully managed by <br />Google. <br />2. This is not applicable. With the Google IaaS solutions all server images are provided by <br />Google. <br />3. With respect to the SaaS offfering, Google Apps, if customers have not selected the Google <br />Apps Unlimited option which offers unlimited storage, they have options to upgrade. With respect <br />to the PaaS/laaS offering, Google Cloud Platform, storage space is allocated dynamically based <br />on actual usage demand. <br />4. SaaS, Google Apps includes numerous administrative tools to monitor end user and <br />administrator activites." <br />AODocs <br />This is not applicable. <br />Virtru <br />AMIs provisioned using terraform and configured by Ansible to include all configuration <br />parameters <br />Salesforce <br />This is not applicable. These services while applicable to IaaS are not applicable to PaaS/SaaS <br />where all of the infrastructure is managed by Salesforce as the Cloud Service Provider. These <br />services are included and managed as part of the Salesforce subscription service and not directly <br />exposed to the customer. <br />The multitenant architecture and secure logical controls address separation of customer data. <br />There are no dedicated servers used for individual customers. The Salesforce Services <br />infrastructure is divided into a modular architecture based on "Instance". Each Instance is capable <br />of supporting several thousand customers in a secure and efficient manner. Services are grouped <br />within each Instance; with app, search, and database elements contained. There are appropriate <br />controls in place to ensure that any given customer's org (application) is not compromised. The <br />service has been designed to accomplish this and is robustly tested on an ongoing basis by both <br />Salesforce and its customers. <br />An instance consists of a database instance run on clustered database servers and physical <br />storage subsystems. Each server has been allocated a different volume group so it can fail over to <br />its backup server within the instance independently of the others. As scalability needs dictate, <br />carahsoft 170 carahsoft <br />