Cloud Search Platform
Cloud Search Platform enables companies to quickly, easily and securely search for information across their business. Cloud Search utilizes machine learning to bring instant query suggestions and surface the most relevant results across different content systems — in over 100 different languages.
- Robust SDKs
- Ready-to-use APIs
- Index content from 60+ enterprise sources
- Granular access-level controls
- Trusted infrastructure
- Supports Google web search
- Searching through your company’s data becomes easier.
- Machine-learning bringing instant query suggestions and surface relevant results
- Looks-through different content systems in over 100 different languages.
- Cloud search helps-you scalably index vast-amounts of data from any-source.
- With 80+ connectors, index third-party content from 60+ enterprise sources.
- Search results reflect the security models you choose.
- Retrieve information from internal data repositories.
- Search interface can be developed for use on any device
- Indexes G Suite data, such as Google documents and spreadsheets.
£0 per unit
+44 20 7346 2879
|Software add-on or extension||No|
|Cloud deployment model||Public cloud|
|Service constraints||Please refer to our Service Definition document and Supplier Terms for the applicable service.|
|System requirements||A modern web browser|
|Email or online ticketing support||Email or online ticketing|
|Support response times||
Target initial response time for written P1 Priority support requests is one hour and are responded to 24 x 7. Target initial response time for written P2, P3, and P4 Priority support requests submitted via Online Help Center or support portal is 1 business day or less.
Priorities are defined here: https://support.google.com/a/answer/1047213
All Support services are outlined in the technical support services guidelines: https://gsuite.google.com/terms/tssg.html
*NOTE: These terms apply to all G Suite versions except G Suite for Education version, response may be different.
**NOTE: Phone support is not available with the free edition of G Suite or Cloud Identity.
|User can manage status and priority of support tickets||No|
|Phone support availability||24 hours, 7 days a week|
|Web chat support||Web chat|
|Web chat support availability||24 hours, 7 days a week|
|Web chat support accessibility standard||WCAG 2.1 AAA|
|Web chat accessibility testing||It is in our pipeline to test and deliver our products and services to become more accessible for assistive technology users|
|Support levels||All G Suite customers are eligible for Standard support at not additional cost. Standard support services are described further here: in the TSSG: https://gsuite.google.com/terms/tssg.html.|
|Support available to third parties||No|
Onboarding and offboarding
"Google provides a business transformation framework based on research in accredited universities. An online Getting Started learning path is described at https://gsuite.google.com/setup/
We also povide G suite training which is a plug-in to your Chrome and describes step-by step functionalities and processes.
The G suite Learning Center https://gsuite.google.com/learning-center/ provides numerous documentation, guides, tips, customer examples, and training resources"
|Other documentation formats||Contextual training videos|
|End-of-contract data extraction||"We provide tools to our customers to export their data. More information can be found here: https://support.google.com/a/answer/100458?hl=en#all"|
"For information on offboarding, please refer to:
Using the service
|Web browser interface||Yes|
|Application to install||Yes|
|Compatible operating systems||
|Designed for use on mobile devices||Yes|
|Differences between the mobile and desktop service||We've written native applications for Android and iOS which are designed with those user interface frameworks in mind|
|Accessibility standards||None or don’t know|
|Description of accessibility||Google’s conformance to WCAG 2.0 AAA guidelines is documented in Google’s VPAT reports online here: https://support.google.com/a/answer/2821355?hl=en#h4_vpats|
|Accessibility testing||It is in our pipeline to test and deliver our products and services to become more accessible for assistive technology users|
|What users can and can't do using the API||The scope of capabilities exposed via API to GSuite/Cloud Identity/Drive/Cloud Search Platform users is very broad and encompasses most major use cases. API's are can be found here: https://developers.google.com/|
|API documentation formats||
|API sandbox or test environment||Yes|
|Description of customisation||
With Apps Script, you can create Add-ons for Google Docs, Macros, menus, and custom functions as well as managing responses for Google Forms"
|Independence of resources||G Suite provides scalable and elastic cloud services.|
|Service usage metrics||Yes|
"- Highlights: Key metrics and trends including app usage, users status, file visibility, and security.
- Security: Assess overall exposure to data breach. Discover which users not using 2-step verification, installing external apps, or sharing documents indiscriminately.
- Apps Usage Activity: See how your organization uses G Suite over a specific period by examining email activity, number of spreadsheets created, number of files shared, and more.
- Account Activity: Access all data from Security, Apps Usage Activity, and Highlights pages in a single master report.
- Audits: View logs of various activity, including admin, mobile activity, and more.
|Supplier type||Not a reseller|
|Staff security clearance||Other security clearance|
|Government security clearance||None|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||
|User control over data storage and processing locations||No|
|Datacentre security standards||Complies with a recognised standard (for example CSA CCM version 3.0)|
|Penetration testing frequency||At least every 6 months|
|Penetration testing approach||In-house|
|Protecting data at rest||
|Other data at rest protection approach||
"Data belonging to G Suite customers is stored at rest in two types of systems: disks and backup media.
Disks are used to write and retrieve data in multiple replicated copies. (For more information on this replication of data, please see the G Suite Security Whitepaper.) Google also stores data on offline backup media to help ensure recovery from any catastrophic error or natural disaster at one of our data centers.
Data stored at rest is encrypted on both disks and backup media, but for each system we use a distinct approach for encryption to mitigate the corresponding security risks."
|Data sanitisation process||Yes|
|Data sanitisation type||Explicit overwriting of storage before reallocation|
|Equipment disposal approach||Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001|
Data importing and exporting
|Data export approach||
"Please refer to
|Data export formats||
|Other data export formats||
|Data import formats||
|Other data import formats||
|Data protection between buyer and supplier networks||TLS (version 1.2 or above)|
|Data protection within supplier network||TLS (version 1.2 or above)|
Availability and resilience
|Guaranteed availability||During the Term of the applicable G Suite Agreement (or prior versions of the agreement governing the use of G Suite) (the "Agreement"), the (i) G Suite Covered Services web interface will be operational and available to Customer at least 99.9% of the time in any calendar month; and (ii) Google Voice will be operational within 2 business days of Customer's acceptance of the Voice Service Specific Terms via the Admin Console (the "G Suite SLA"). If Google does not meet the G Suite SLA, and if Customer meets its obligations under this G Suite SLA, Customer will be eligible to receive the Service Credits described below. This G Suite SLA states Customer's sole and exclusive remedy for any failure by Google to meet the G Suite SLA.|
|Approach to resilience||All data is redundantly stored across a minimum of 3 data centers, and all services are designed to leverage the redundant data center infrastructure powering Google services.|
Please refer to the link below
Identity and authentication
|User authentication needed||Yes|
|Other user authentication||
"A built-in Password Monitor is visible to the end user upon password
creation and to the System Administrators of the tenant whom can decide to force a password change on any user that is later detected to have a password that is weak. Google's native authentication has
protections in place that would detect a brute force attack and challenge the user to solve a Captcha and would auto lock the account if suspicious activity is detected. The tenant's System Administrators can
reset that account for the end user."
|Access restrictions in management interfaces and support channels||
"G Suite provides administrative features made available to Customer within the Admin Console for the management of Google-hosted accounts, mobile devices, and application within the Customer’s domain. Advanced security and control features may be subject to an additional charge
Support services are only provided to authorized customer administrators whose identities have been verified in several ways. Googler access is monitored and audited by our dedicated security, privacy, and internal audit teams.
|Access restriction testing frequency||At least once a year|
|Management access authentication||
|Description of management access authentication||
Google's native authentication requires a minimum 8 character complex password. Tenants can set the
maximum or increase the minimum. A Password Monitor is visible to the end user upon password
creation and to the System Administrators of the tenant. Google's native authentication has
protections in place that would detect a brute force attack and challenge the user if suspicious activity is detected. System Administrators can reset that account for the end user.
Google provides the capability for domain administrators to enforce Google's 2-step verification. The 2nd
factor could be a code generated via several supported mechanisms.
Audit information for users
|Access to user activity audit information||Users have access to real-time audit information|
|How long user audit data is stored for||Less than 1 month|
|Access to supplier activity audit information||Users receive audit information on a regular basis|
|How long supplier audit data is stored for||At least 12 months|
|How long system logs are stored for||User-defined|
Standards and certifications
|ISO/IEC 27001 certification||Yes|
|Who accredited the ISO/IEC 27001||EY CertifyPoint|
|ISO/IEC 27001 accreditation date||18 December 2018|
|What the ISO/IEC 27001 doesn’t cover||See certificate for full list of products covered, anything not listed is not covered. See the certificate link: https://services.google.com/fh/files/misc/gcp_iso27001_fall_2018.pdf|
|ISO 28000:2007 certification||No|
|CSA STAR certification||Yes|
|CSA STAR accreditation date||02/05/2018|
|CSA STAR certification level||Level 2: CSA STAR Attestation|
|What the CSA STAR doesn’t cover||The supported list of services is available at https://cloud.google.com/security/compliance/csa-star/|
|Who accredited the PCI DSS certification||PCI Attestation of Compliance available under NDA.|
|PCI DSS accreditation date||PCI Attestation of Compliance available under NDA.|
|What the PCI DSS doesn’t cover||The supported list of services is available at https://cloud.google.com/security/compliance/pci-dss/|
|Other security certifications||Yes|
|Any other security certifications||Full list available at https://cloud.google.com/security/compliance/#/|
|Named board-level person responsible for service security||Yes|
|Security governance certified||Yes|
|Security governance standards||CSA CCM version 3.0|
|Information security policies and processes||
"Google's cloud services are designed to deliver better security than many traditional on-premises solutions. Google makes security, and protection of data it's primary design criteria, which is the cornerstone of it's overall security governance and compliance audits. Google’s third party audit approach is designed to be comprehensive to provide assurances of Google’s information security capabilities. Customers may use these third party audits to assess how Google’s products can meet their compliance and data-processing needs.
|Configuration and change management standard||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Configuration and change management approach||In Google production environments, software updates are manually vetted to ensure the stability of the system. Changes are then tested and cautiously rolled out to systems. The details vary somewhat depending on the service being considered, but all development work is separated from the operation systems, testing occurs in a multi-staged fashion in both environments and in dedicated test settings. We can share, under NDA, the SOC2 audit report (based on standards from the International Auditing and Assurance Standards Board), which describes the change management process. Additionally, changes to code go through a process of code review involving additional engineer(s).|
|Vulnerability management type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Vulnerability management approach||
"Google administrates a vulnerability management process that actively scans for security threats using a combination of commercially available and purpose-built in-house tools, intensive-automated and manual penetration efforts, quality assurance processes, software security reviews and external audits. The vulnerability management team is responsible for tracking and following up on vulnerabilities. Once a vulnerability requiring remediation has been identified, it is logged, prioritized according to severity, and assigned an owner. The vulnerability management team tracks and follows up frequently until remediated. Google also maintains relationships with members of the security research community to track issues in Google services and open-source tools.
|Protective monitoring type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Protective monitoring approach||
"At many points across our global network, internal traffic is inspected for suspicious behavior, such as the presence of traffic that might indicate botnet connections. This analysis is performed using a combination of open-source and commercial tools for traffic capture and parsing. A proprietary correlation system built on top of Google technology also supports this analysis. Network analysis is supplemented by examining system logs to identify unusual behavior, such as attempted access of customer data. Google security engineers place standing search alerts on public data repositories to look for security incidents that might affect the company’s infrastructure.
|Incident management type||Conforms to a recognised standard, for example, CSA CCM v3.0 or ISO/IEC 27035:2011 or SSAE-16 / ISAE 3402|
|Incident management approach||
"We have a rigorous incident management process for security events that may affect the confidentiality, integrity, or availability of systems or data. This process specifies courses of action, procedures for notification, escalation, mitigation, and documentation. Google’s security incident management program is structured around the NIST guidance on handling incidents (NIST SP 800–61). Key staff are trained in forensics and handling evidence in preparation for an event, including the use of third-party and proprietary tools. Testing of incident response plans is performed for key areas, such as systems that store sensitive customer information.
|Approach to secure software development best practice||Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v3.0)|
Public sector networks
|Connection to public sector networks||No|
|Price||£0 per unit|
|Discount for educational organisations||No|
|Free trial available||No|