Laserfiche WebLink
SOLICITATION # CH16012 <br />officer monitors the entrance to prevent tailgating. Where present, the portal/mantrap <br />bypass doors are only used in the event an individual is unable to use the portal or <br />mantrap in case of emergency. Examples include handicap, phobia, or other <br />restrictions on a case -by -case basis. Tours and emergency data center security <br />operations crews will be permitted to use the portal bypass door, when necessary. <br />ASM <br />Physical access mechanisms (e.g., access cards, biometric devices, mantraps and <br />portals) have been implemented and are administered by local operations staff to help <br />ensure that only authorized individuals have the ability to access the data centers. <br />Portals and mantraps have been installed as anti -tailgating measures in most of data <br />center lobbies. Entry to and exit from the data centers is through either a portal or <br />mantrap where present. In data centers without portals or mantraps, the security <br />officer monitors the entrance to prevent tailgating. Where present, the portal/mantrap <br />bypass doors are only used in the event an individual is unable to use the portal or <br />mantrap in case of emergency. Examples include handicap, phobia, or other <br />restrictions on a case -by -case basis. Tours and emergency data center security <br />operations crews will be permitted to use the portal bypass door, when necessary. <br />AODocs <br />N/A because all our data is hosted on the Google Cloud Platform infrastructure. <br />Virtru <br />We require 2 Factor and Private Keys to authenticate and Virtrual Private Clouds for purposes of <br />Inter -machine communication <br />Salesforce <br />A customer's instance (org) of Salesforce is an aggregate of the raw data. The data model is very <br />complicated, normalized, and the rows are identified by base62 encoded keys (primary and <br />foreign). Re-establishing data ownership and a business context for the data would be very difficult <br />to do at the database level. In order to reassemble any given customer's application (org), <br />someone would need access to our source code in order to reassemble the raw data in a manner <br />that could be interpreted and understood, and would need the entire set of tapes or disks/arrays <br />supporting a given Instance, as the data for any one customer is spread across several <br />tapes/disks. Data center engineers with physical access to the servers do not have logical access <br />to the production environment and administrators with logical access to the systems do not have <br />physical access to the data centers. <br />ServiceNow <br />ServiceNow's architecture is built on a ServiceNow fully owned operated private cloud. This <br />private cloud hosts the ServiceNow platform and applications that are offered to its customers <br />under a subscription service model. The ServiceNow private cloud operates out of colocation data <br />centers that provide robust physical and environmental controls, with ServiceNow staff exclusively <br />providing the logical management. Access to the private cloud where customer data is hosted is <br />only granted to ServiceNow staff based on their roles and job requirements. ServiceNow does not <br />outsource any function that would give a third party access to customer data. <br />ServiceNow's private cloud is a highly standardized environment from the identically configured <br />cages in the data centers through to the consistent logical infrastructure. This private cloud is <br />home to just ServiceNow, limiting the private cloud's footprint to only those technologies required <br />to support this service. This allows for highly restricted networking rule sets regarding ingress and <br />egress requirements and facilitates the ability for hardened systems, only allowing for the small <br />number of necessary services, protocols and ports to be enabled. <br />A ServiceNow instance represents an isolated logical environment consisting of application nodes <br />in the web application tier and a dedicated database. Each customer will receive at least two <br />instances, a production High Availability (HA) instance and a sub -production instance without HA. <br />Each instance is accessed via a unique Domain name in the form of'customername.service- <br />now.com' (for a production instance) and 'customername-dev.service-now.com' as a sub - <br />production example. <br />carahsoft <br />85 <br />carahsoft <br />