2 Responsibilities
As retailers migrate to the cloud, they must consider how the cloud, and more specifically Software-As-A-Service (SaaS), will impact their privacy, security, and compliance efforts. As the cloud service provider, Oracle Retail works together with customers to meet cloud security objectives.
Retailer Responsibilities
At a high level, retailers are responsible for:
-
Understanding Oracle's security policies
-
Implementing their own corporate policies via Oracle tools
-
Creating and administering users via Oracle tools
-
Ensuring data quality and enforcing end-user devices security controls, so that antivirus, malware, and other malicious code checks are performed on data and files before uploading data
-
Ensuring that end-user devices meet the minimum security requirements
-
Generating public/private key pairs as requested by Oracle Retail
To securely implement Retail Analytics & Planning applications, retailers and their implementation partners should read this document to understand Oracle's security policies. This document summarizes information and contains links to many other Oracle documents.
Oracle Responsibilities
As the cloud service provider, at the highest level Oracle Retail is responsible for:
-
Building secure software
-
Provisioning and managing secure environments
-
Protecting the retailer's data
Retail Analytics & Planning applications fulfill their responsibilities by a combination of corporate level development practices and cloud delivery policies. Sections in this document will describe this information in great detail later in this document.
Security Category Definitions
To discuss Retail Analytics & Planning Cloud Services SaaS security, it helps to define and categorize the many aspects of security. For the purposes of this document, we discuss the following categories of SaaS security:
Secure Product Engineering
Oracle builds secure software through a rigorous set of formal, always evolving security standards and practices known as Oracle Software Security Assurance (OSSA). OSSA encompasses every phase of the product development lifecycle.
More information about OSSA can be found at:
https://www.oracle.com/corporate/security-practices/assurance/
The cornerstones of OSSA are Secure Coding Standards and Security Analysis and Testing. Secure Coding Standards include both general use cases and language-specific security practices. More information about these practices can be found at:
https://www.oracle.com/corporate/security-practices/assurance/development/
Security Analysis and Testing includes product-specific functional security testing and both static and dynamic analysis of the code base. Static Analysis is performed through tools including both internal Oracle tools and HP's Fortify. Dynamic Analysis focuses on APIs and endpoints, using techniques like fuzzing to test interfaces and protocols.
https://www.oracle.com/corporate/security-practices/assurance/development/analysis-testing.html
Secure Deployment
Secure deployment refers to the security of the infrastructure used to deploy the SaaS application. Key issues in secure deployment include Physical Safeguards, Network Security, Infrastructure Security and Data Security.
Physical Safeguards
Retail Analytics & Planning Cloud Services are deployed through Oracle Cloud Infrastructure datacenters. Access to Oracle Cloud data centers requires special authorization that is monitored and audited. The premises are monitored by CCTV, with entrances protected by physical barriers and security guards. Governance controls are in place to minimize the resources that are able to access systems. Physical security safeguards are further detailed in Oracle's Cloud Hosting and Delivery Policies.
http://www.oracle.com/us/corporate/contracts/ocloud-hosting-delivery-policies-3089853.pdfNetwork Security
The Oracle Cloud network is isolated from the Oracle Corporate Network. Customer instances are separated down to the VLAN level.
Infrastructure Security
The security of the underlying infrastructure used to deploy Retail Analytics & Planning Cloud Services is regularly hardened. Critical patch updates are applied on a regular schedule. Oracle maintains a running list of critical patch updates and security alerts. Per Oracle's Cloud Hosting and Delivery Policies, these updates are applied to all Oracle SaaS systems.
https://www.oracle.com/technetwork/topics/security/alerts-086861.htmlBefore our Cloud Services deploy code to SaaS, Oracle's Global Information Security team performs penetration testing on the cloud service. This penetration testing and remediation prevents software or infrastructure issues in production systems.
https://www.oracle.com/corporate/security-practices/assurance/development/ethical-hacking.htmlData Security
Retail Analytics & Planning Cloud Services uses a number of strategies and policies to ensure the retailer's data is fully secured.
-
Data Design – Our applications avoid storing personal data unless required. Where PII data exists in a system, Data Minimization, Right to Access, and Right to Forget services exist to support data privacy standards.
-
Storage - Our applications use encrypted tablespaces to store sensitive data.
-
Transit - All data is encrypted in transit; Retail SaaS uses TLS for secure transport of data, as documented in Oracle's Cloud Hosting and Delivery policy:
https://www.oracle.com/assets/ocloud-hosting-delivery-policies-3089853.pdf
Our cloud services also implement data filtering so that users see the data stripes relevant to their own jobs, as detailed later in this document.
Secure Management
Oracle Cloud Services manage SaaS based on a well-documented set of security-focused Standard Operating Procedures (SOPs). The SOPs provide direction and describe activities and tasks undertaken by Oracle personnel when delivering services to customers. SOPs are managed centrally and are available to authorized personnel through Oracle's intranet on a need-to-know basis.
All network devices, servers, operating systems, applications, and databases underlying our Cloud Services are configured and maintain auditing and logging. All logs are forwarded to a Security Information and Event Management (SIEM) system. The SIEM is managed by the Security Engineering team and is monitored 24*7 by the GBU Security Operations team. The SIEM is configured to alert the GBU Security Operations team regarding any conditions deemed to be potentially suspicious, for further investigation. Access given to review logs is restricted to a subset of security administrators and security operations personnel only.