Laserfiche WebLink
SOLICITATION # CH16012 <br />designed electronic access cards, alarms, vehicle access barriers, perimeter fencing, metal <br />detectors, and biometrics, and the data center floor features laser beam intrusion detection. Our <br />data centers are monitored 24/7 by high -resolution interior and exterior cameras that can detect <br />and track intruders. Access logs, activity records, and camera footage are available in case an <br />incident occurs. Data centers are also routinely patrolled by experienced security guards who have <br />undergone rigorous background checks and training. As you get closer to the data center floor, <br />security measures also increase. Access to the data center floor is only possible via a security <br />corridor which implements multifactor access control using security badges and biometrics. Only <br />approved employees with specific roles may enter. Less than one percent of Googlers will ever <br />step foot in one of our data centers. <br />Google operates a global, multi -tenant environment running the world's second largest IP data <br />network providing customers with a low latency, high performing platform that runs 247. <br />Hard Disks are assets that are tracked throughout its lifecycle at Google from arrival to final <br />destruction. These disks are component parts that Google uses to build its own servers from <br />other component parts including motherboards and a harden, highly customized version of Linux. <br />Google uses a proprietary storage and processing mechanism that isolates processing of data in <br />chrooted jails within a physical server. Access permissions restrict the ability for processes to <br />interact between jails. In addition, tenant data is striped in chunks across many different drives <br />with each chunk having its own access control list. This helps ensure that data is logically isolated <br />between customers in storage and during processing. <br />In addition to the inherent processing and storage mechanisms described above, Google's <br />security controls including least privilege rights, logging and auditing have been implemented <br />consistent with FedRAMP requirements <br />AODocs <br />Altirnao can use multiple notification channels to communicate incident updates to its customers: <br />the AODocs status page (https://status.aodocs.com) provide status updates on all the AODocs <br />services the AODocs customer mailing list, which can be used to send emails to the technical <br />contacts of all AODocs customers the AODocs support platform, i.e. ZenDesk, which can be used <br />to communicate with specific customers who have opened tickets. <br />Salesforce <br />Incident Response <br />If negotiated into a final contract, Salesforce can promptly notify the Customer in the event <br />Salesforce becomes aware of an actual or reasonably suspected unauthorized disclosure of <br />Customer Data. Notification may include phone contact by Salesforce support, email to customer's <br />administrator and Security Contact (if submitted by customer), and public posting on <br />trust. salesforce.com. <br />Salesforce maintains an Incident Response Plan and has an established Security Incident <br />Response Process. During a security incident, the process guides Salesforce personnel in <br />management, communication, and resolution activities. Government customers can report security <br />incidents related to their Salesforce products and offerings via security_gov@salesforce.com. <br />Salesforce will respond in accordance with the incident response process described above. <br />Our incident response plan/process was created in accordance with FedRAMP moderate control <br />requirements which include incident response requirements derived from NIST SP 800-53, NIST <br />SP 800-61, and the FedRAMP Incident Communications Procedure. <br />ServiceNow <br />Unless notification is delayed by the actions or demands of a law enforcement agency, <br />ServiceNow shall report to Customer the unauthorized acquisition, access, use, disclosure or <br />destruction of Customer Data (a "Breach") promptly following determination by ServiceNow that a <br />Breach occurred. The initial report shall be made to Customer security contacts designated in <br />carahsoft 80 carahsoft <br />