Skip to content

Commit 9a88ab1

Browse files
committed
cloud security
1 parent a2bb983 commit 9a88ab1

File tree

2 files changed

+89
-0
lines changed

2 files changed

+89
-0
lines changed

docs/.vuepress/sets/craft-cloud.js

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,7 @@ module.exports = {
7878
children: [
7979
"faq",
8080
"troubleshooting",
81+
"security",
8182
],
8283
},
8384
],

docs/cloud/security.md

Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,88 @@
1+
# Security
2+
3+
Craft Cloud is designed as a fully managed, secure cloud PaaS hosting platform optimized for Craft CMS applications.
4+
5+
This document outlines the security principles, controls, and practices that govern ****Craft Cloud to protect customer applications, data, and infrastructure against unauthorized access and vulnerabilities.
6+
7+
## Shared Responsibility Model
8+
9+
Security in Craft Cloud environments follows the industry standard cloud shared responsibility model:
10+
11+
- Craft Cloud’s responsibilities:
12+
- Underlying infrastructure
13+
- Network security
14+
- Platform configuration
15+
- Service availability and stability
16+
17+
- Customer’s Responsibilities:
18+
- Keep Craft CMS, plugins, and dependencies up to date, including the Craft Cloud extension
19+
- Manage application credentials securely
20+
- Implement secure coding practices to prevent common vulnerabilities
21+
- Review application logs
22+
23+
## Infrastructure & Platform Security
24+
25+
### Physical and Cloud Provider Controls
26+
27+
Craft Cloud’s infrastructure runs on industry-leading cloud providers that implement robust controls. These companies use fully SOC-2 compliant access procedures.
28+
29+
You can read more about their compliance and security policies here:
30+
31+
- AWS: https://aws.amazon.com/compliance/
32+
- Cloudflare: https://www.cloudflare.com/trust-hub/compliance-resources/
33+
34+
### Network Security and Segregation
35+
36+
Craft Cloud leverages:
37+
38+
- Enterprise-grade firewalls and DDoS protection
39+
- Encrypted network connections for internal traffic
40+
- Isolation of customer environments to prevent unauthorized lateral movement
41+
42+
Every Craft Cloud project includes firewall and global CDN protections by default.
43+
44+
Since portions of Craft Cloud are multi-tenant, it utilizes some shared infrastructure across projects. To ensure that different projects cannot communicate with each other, it maintains strict network segregation between components.
45+
46+
### Ephemeral Filesystems
47+
48+
All Craft Cloud projects run on a read-only, ephemeral file system, which offers some inherent security benefits. If a site is compromised, redeploying will remove any scripts or payloads left behind and reset the code to a known good state prior to the compromise.
49+
50+
## Data Protection
51+
52+
- Databases and backups are fully encrypted, with encryption provided by the underlying storage service providers.
53+
54+
### Backups and Recovery
55+
56+
- Daily automated database backups are performed for all customer projects
57+
- Customers can trigger optional manual backups
58+
- Backups are retained for 30 days.
59+
60+
## Identity and Access Management
61+
62+
### Platform Access Controls
63+
64+
Craft Cloud enforces role-based access controls via Craft Console Organizations. Customers are highly encouraged to create their Craft Cloud projects within a Craft Console Organization to take advantage of these role-based access controls.
65+
66+
### Two-Factor Authentication (2FA)
67+
68+
Customers are highly encouraged to enable two-factor authentication (2FA) for their Craft Console accounts, as well as for their Craft installations hosted on Craft Cloud.
69+
70+
### Staff Access
71+
72+
Craft Cloud staff have secure access to client projects, but will only access that data for the purposes of debugging and supporting the customer.
73+
74+
## Incident Response and Monitoring
75+
76+
Craft Cloud incorporates monitoring for:
77+
78+
- Unauthorized access attempts
79+
- Anomalous platform activity
80+
- Infrastructure alerts
81+
82+
Customers are notified of incidents via [https://status.craftcms.com](https://status.craftcms.com/) where they can subscribe to any incidents and updates.
83+
84+
## Reporting a Vulnerability
85+
86+
Please report any security vulnerabilities to [[email protected]](mailto:[email protected]).
87+
88+
You can read our policy on reporting vulnerabilities here: [https://github.com/craftcms/cms/security/policy](https://github.com/craftcms/cms/security/policy).

0 commit comments

Comments
 (0)