Symantec Data Loss Prevention Cloud Service Connector for Web Site Security Service
The Symantec Data Loss Prevention Cloud Service Connector is a Symantec Data Loss Prevention detection service deployed in the cloud that enables you to monitor content and identify information policy violations in web traffic. bsscloud
- DLP content inspection for web traffic.
- Cloud based detection service, in the cloud, for the cloud.
- Inspects HTTP,HTTPS and FTP traffic.
- Block data in motion.
- Granular configuration for traffic sources.
- No programming development effort required to integrate with Symantec WSS
- Leverage your existing Symantec DLP policies.
- Get faster performance running DLP detection as a service.
- No need to back haul traffic to on-premise detection servers.
- Reduce information leakage via web sites
£0.00 per person
Bytes Software Services
+44 (0) 7951 326815
|Software add-on or extension||Yes|
|What software services is the service an extension to||
Symantec Cloud Web Security Service.
Symantec DLP management platform.
|Cloud deployment model||Public cloud|
|Email or online ticketing support||Email or online ticketing|
|Support response times||
Severity1: (i) your production server or other mission critical system is down or has a substantial loss of service; (ii) a substantial portion of your mission critical data is at a significant risk of loss or corruption.
Target (following acknowledgement): within 30 minutes.
Severity2: A problem where a major functionality is severely impaired. Operations can continue in a restricted fashion.
Target :within 2 hours
Severity 3: Limited adverse effect on business operations.
Target response: by same time the next business day
Severity 4: Problem where your business operations have not been adversely affected.
Target response: within the next business day
|User can manage status and priority of support tickets||Yes|
|Online ticketing support accessibility||None or don’t know|
|Phone support availability||24 hours, 7 days a week|
|Web chat support||No|
Essential support includes 24 hours, 7 days a week support - included in the price schedule attached to this service.
Additional service offerings include: Customer Success Premium (additional to the supplied pricing data):
A Customer Success Manager who tailors Symantec solutions to meet business requirements, risk management and customisation services, instructor-led training, and priority access to more experienced support engineers, 24x7.
Customer Success Select (additional to the supplied pricing data)
A single point of contact, plus access to a designated expert in a specific product family, and priority access to more experienced support engineers, 24x7.
Customer Success Core (additional to the supplied pricing data):
A single point of contact plus priority access to more experienced support engineers, 24x7.
Pricing for the 'Customer Success' support offerings start at $20k. Full details are available on request
|Support available to third parties||Yes|
Onboarding and offboarding
Comprehensive documentation is provided. A digital configuration bundle is supplied to your Symantec DLP administrator. It can be imported directly into the DLP management server.
Further information can be viewed here: https://support.symantec.com/en_US/article.DOC9414.html
|End-of-contract data extraction||All data will already be stored in your on premise Symantec DLP installation. This cloud service is an add-on to Symantec DLP.|
|End-of-contract process||At the end of the contract the service will cease to scan data.|
Using the service
|Web browser interface||Yes|
|Application to install||No|
|Designed for use on mobile devices||Yes|
|Differences between the mobile and desktop service||All detection is carried out in a cloud environment so there is no difference in service regardless of the endpoint being used. Covers all supported traffic types that are routed through Symantec Cloud Web Security Service.|
|What users can and can't do using the API||
The Symantec Data Loss Prevention Cloud Service Connector REST API lets you create a REST client for your cloud application to enable integration with Symantec Data Loss Prevention. Your REST API client sends sensitive data to Symantec Data Loss Prevention for inspection by way of the Cloud Service Connector. Symantec Data Loss Prevention inspects the data and creates incidents where applicable. Symantec Data Loss Prevention also returns response action recommendations in the REST detection request response.
A sandbox environment, provided under a separate licence, can be procured if required.
|API documentation formats|
|API sandbox or test environment||Yes|
|Description of customisation||Buyers can create and manage their own data loss prevention policies in line with their requirements.|
|Independence of resources||The Services are designed ground-up to be resilient by providing highly-available regions. The Detection Servers (Detectors) are provisioned on-demand as a pool (more than one) and elastically scale depending on the workload. All DLP Cloud services are loosely-coupled and designed to be flexible and redundant.|
|Service usage metrics||No|
|Supplier type||Reseller providing extra support|
|Organisation whose services are being resold||Symantec|
|Staff security clearance||Other security clearance|
|Government security clearance||Up to Baseline Personnel Security Standard (BPSS)|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||
|User control over data storage and processing locations||Yes|
|Datacentre security standards||Complies with a recognised standard (for example CSA CCM version 3.0)|
|Penetration testing frequency||At least once a year|
|Penetration testing approach||In-house|
|Protecting data at rest||Other|
|Other data at rest protection approach||The service applies multiple levels of encryption to protect the confidentiality and integrity of customer data (policies, profiles, incidents, etc.). The top level keys are managed by AWS KMS, and individual keys are protected by customer-specific IAM roles. All encryption is AES with 128- and 256-bit keys.|
|Data sanitisation process||No|
|Equipment disposal approach||In-house destruction process|
Data importing and exporting
|Data export approach||
All data is stored in the related DLP management server, rather than within the service component described here.
DLP incident data can be exported from the DLP Management server in CSV format. The export mechanism supports the bulk export of this data.
|Data export formats||
|Other data export formats||XML|
|Data import formats||Other|
|Other data import formats||There is no requirement to upload data.|
|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||Details available on request.|
|Approach to resilience||The DLP service component is designed from the ground-up to be resilient by providing highly-available regions. The Detection Servers (Detectors) are provisioned on-demand as a pool (more than one) and elastically scale depending on the workload. All DLP Cloud services are loosely-coupled and designed to be flexible and redundant.|
|Outage reporting||Where Emergency Maintenance is necessary and is likely to affect the Service, Symantec will endeavor to inform the affected Customers in advance by delivering an alert via email no less than one (1) hour prior to the start of the Emergency Maintenance.|
Identity and authentication
|User authentication needed||No|
|Access restrictions in management interfaces and support channels||Access management for administrators is controlled through the cloud based console. End users do not interact directly with the service. Symantec access to the cloud infrastructure is controlled both by two factor authentication, and IP address whitelist, such that only relevant Symantec personnel can access the systems.|
|Access restriction testing frequency||At least once a year|
|Management access authentication||Username or password|
Audit information for users
|Access to user activity audit information||Users contact the support team to get audit information|
|How long user audit data is stored for||At least 12 months|
|Access to supplier activity audit information||Users contact the support team to get audit information|
|How long supplier audit data is stored for||At least 12 months|
|How long system logs are stored for||At least 12 months|
Standards and certifications
|ISO/IEC 27001 certification||No|
|ISO 28000:2007 certification||No|
|CSA STAR certification||No|
|Other security certifications||Yes|
|Any other security certifications||Data centers SOC 2 type 2 reports or ISO 27001|
|Named board-level person responsible for service security||Yes|
|Security governance certified||No|
|Security governance approach||We have an ISMS committee who are responsible for day to day management of the ISMS system. That committee is headed by a senior manager who is responsible for compliance and customer assurance. That committee reports to a governance committee responsible for all applicable standards compliance, which then reports to the business owner of the service.|
|Information security policies and processes||All staff are required to read and comply with our security policies. Staff are trained in line with our security practices. Our Chief Security Officer reports directly to Symantec's General Counsel. Our policies and processes include, but are not limited to, security, incident response, business continuity, secure software development and supply chain risk management. External versions of a number of our policies are available here: https://www.symantec.com/about/customer-trust-portal|
|Configuration and change management standard||Supplier-defined controls|
|Configuration and change management approach||Any changes in production infrastructure have to be tested and certified in the Continuous Integration/ Continuous Delivery (CI/CD) pipeline. Changes are nominated, tested, certified, and promoted to production. Sprint cadence is currently every 3 weeks. Lastly, infrastructure changes are infrequent, ticketed, and done by updating templates rather than making manual changes.|
|Vulnerability management type||Supplier-defined controls|
|Vulnerability management approach||Symantec has a formal process for handling and managing vulnerabilities. For any externally reported issues, Symantec follows the process outlined in ISO 29147, Information technology — Security techniques — Vulnerability disclosure ([ISO/IEC 29147:2014(E)]). Symantec'c Software Security Group works with the impacted team(s) to: • Recreate the environment and issue within Symantec’s labs for an expedited resolution. • Facilitate a prompt and accurate response. • Avoid delays in new Symantec releases.|
|Protective monitoring type||Supplier-defined controls|
|Protective monitoring approach||Please contact Symantec for a more in depth discussion about our controls.|
|Incident management type||Supplier-defined controls|
|Incident management approach||Symantec’s internal Security Incident Response Plan documents repeatable, industry standard procedures for handling actual cyber threats when they arise. It also provides the necessary engagement and information-sharing processes to allow prompt coordination among all relevant stakeholders, and describes the reporting, communication, containment, investigation, and recovery mechanisms that exist to support a comprehensive end-to-end process flow from threat detection through remediation. The development and implementation of this forward-looking plan supports Symantec’s ultimate mission to its customers, partners, shareholders, and employees as a trusted leader in information security risk management.|
|Approach to secure software development best practice||Supplier-defined process|
Public sector networks
|Connection to public sector networks||No|
|Price||£0.00 per person|
|Discount for educational organisations||No|
|Free trial available||No|