Sitecore took a number of steps to implement the various requirements of the General Data Protection Regulation (GDPR) and California Consumer Protection Act (CCPA) and evolving global privacy laws into Sitecore’s business. This meant building our privacy, security, and data governance teams and continuing to build our data strategy to ensure a robust data model for continuing adherence.
To contact Sitecore’s support team, please submit your support ticket via the Sitecore Support Portal at: support.sitecore.net.
Yes, Sitecore has recently obtained a number of ISO certifications, detailed on the Trust Center security page.
ISO 27001 is a security standard that governs an organization’s Information Security Management System (ISMS) and mandates specific requirements in the implementation, monitoring, maintenance and continuous improvement of the ISMS.
ISO 27017 is a security standard that provides guidance on the information security aspects of cloud computing. Sitecore uses this standard to supplementing the ISO 27001:2013 standard with cloud-specific controls that are applied to its public cloud environment.
ISO 27018 is a code of practice that focuses on protection of personally identifiable information (PII) in the public cloud. By providing cloud services, Sitecore acts as a data processor to its customers. Sitecore uses ISO 27018:2014 standard in order to protect the PII that it processes for its customers
These standards are internationally recognized and demonstrates to our customers, partners and vendors that we have adopted best practices to manage the infrastructure of Sitecore’s ISMS and cloud offerings
Yes, The Knowledge Center on sitecore.com has a variety of topics, including technical articles on topics like SXA and Containers. These Getting Started articles should help you discover the basics.
Products can reach the end of their lifecycle for a number of reasons. For example, this can happen due to market demands, technology innovations that drive changes in the product, or products maturing over time and being replaced by functionally richer technologies.
To help customers better manage this end-of-life transition and to understand the role that Sitecore can play in helping customers use the latest Sitecore platforms and technologies, the Sitecore Product Support Lifecycle policy and matrix are both explained here.
There are a number of reasons why the use of containers is attractive for Sitecore development, and it becomes even more attractive as Sitecore moves towards a microservices-based architecture. Containers lend themselves very well to this architecture (and in fact encourage it).
Other reasons are:
No install - no installation using SIF (Sitecore Installation Framework), SIM (Sitecore Instance Manager), and so on. Sitecore provides container images ready to use. You can get an instance up and running with docker-compose up, and container images will download automatically.
Multi-project efficiencies - you can run multiple Sitecore instances simultaneously without worrying about things like conflicting versions of SQL and Solr. You can start and stop entire instances quickly when jumping between projects.
Simplified onboarding - the onboarding process is as simple as: install prerequisites, clone your code repository, run docker-compose up.
Environment consistency - eliminate issues due to environment inconsistencies. When you containerize your build, you have complete control of the build environment.
Environment stability - because containers are immutable, you do not have to worry about ruining your local Sitecore instance. Use docker-compose down and docker-compose up to get up and running again.
There are many benefits for Sitecore developers