Open Source Platform for DTC, B2B Commerce, Marketplaces & Omnichannel. REST APIs, TypeScript SDKs, and production-ready Next.js storefront. Self-host it. Own your data. No vendor lock-in. Zero platform fees.
Ruby b2b-commercee-commerceecommerceecommerce-apiecommerce-frameworkecommerce-platformheadlessheadless-commerceheadless-ecommercemarketplacemulti-tenantmulti-vendormulti-vendor-ecommerceopen-sourcespree-commerce
[Skip CI] added security policy documentation
Damian Legawiec58024ae0343f
diff --git a/docs/developer/security/api.mdx b/docs/developer/security/api.mdxdeleted file mode 100644index ad1d427d1c..0000000000--- a/docs/developer/security/api.mdx+++ /dev/null@@ -1,18 +0,0 @@-----title: API-section: security-order: 3------# API--<Warning>-This section is only applicatable to API v1-</Warning>--The REST API behaves slightly differently than a standard user. First, an admin has to create the access key before any user can query the REST API. This includes generating the key for the admin him/herself. This is not the case if `Spree::Api::Config[:requires_authentication]` is set to `false`.--In cases where `Spree::Api::Config[:requires_authentication]` is set to `false`, read-only requests in the API will be possible for all users. For actions that modify data within Spree, a user will need to have an API key and then their user record would need to have permission to perform those actions.--It is up to you to communicate that key. As an added measure, this authentication has to occur on every request made through the REST API as no session or cookies are created or stored for the REST API.-diff --git a/docs/developer/security/authentication_and_authorization.mdx b/docs/developer/security/authentication_and_authorization.mdxdeleted file mode 100644index d77247cf67..0000000000--- a/docs/developer/security/authentication_and_authorization.mdx+++ /dev/null@@ -1,33 +0,0 @@-----title: Authentication and Authorization-section: security-order: 2------# Authentication & authorization--If you install spree_auth_devise when setting up your app, we use a third party authentication library for Ruby known as [Devise](https://github.com/plataformatec/devise). This library provides a host of useful functionality that is in turn available to Spree, including the following features:--* Authentication-* Strong password encryption with the ability to specify your own algorithms-* "Remember Me" cookies-* "Forgot my password" emails-* Token-based/oAuth 2.0 access for REST API--## Devise Configuration-- A default Spree install comes with the \[Spree Auth Devise\]https://github.com/spree/spree_auth_devise gem, which provides authentication for Spree using Devise. This section of the guide covers the default setup. If you're using your own authentication, please consult the manual for that authentication engine.--We have configured Devise to handle only what is needed to authenticate with a Spree site. The following details cover the default configurations:--* Passwords are stored in the database encrypted with the salt.-* User authentication is done through the database query.-* User registration is enabled and the user's login is available immediately no validation emails.-* There is a remember me and password recovery tool built in and enabled through Devise.--These configurations represent a reasonable starting point for a typical e-commerce site. Devise can be configured extensively to allow for a different feature set but that is currently beyond the scope of this document. Developers are encouraged to visit the [Devise wiki](https://github.com/plataformatec/devise/wiki) for more details.--## Authorization--Please refer to [Permissions Customization guide](../customization/permissions) for more information.-diff --git a/docs/developer/security/pci_compliance.mdx b/docs/developer/security/pci_compliance.mdxindex 27601af331..c168f37d50 100644--- a/docs/developer/security/pci_compliance.mdx+++ b/docs/developer/security/pci_compliance.mdx@@ -1,13 +1,15 @@-# PCI Compliance+---+title: "PCI Compliance"+----All store owners wishing to process credit card transactions should be familiar with [PCI Compliance](http://en.wikipedia.org/wiki/Pci_compliance). [Spree Gateway Stripe integration](https://github.com/spree/spree_gateway) and [Spree Braintree vzero](https://github.com/spree-contrib/spree_braintree_vzero) are PCI-compliant.+All store owners wishing to process credit card transactions should be familiar with [PCI Compliance](http://en.wikipedia.org/wiki/Pci_compliance). [Spree Stripe](https://github.com/spree/spree_stripe) and [Spree Braintree vzero](https://github.com/spree-contrib/spree_braintree_vzero) are PCI-compliant.-### Using payment tokens+## Using payment tokensWe do not transmit or store Credit Card numbers. Instead we're using payment processor tokens supplied by their SDKs to authorize and charge customer cards.-### 3-D Secure and Strong Customer Authentication support+## 3-D Secure and Strong Customer Authentication support-[Spree Gateway Stripe integration](https://github.com/spree/spree_gateway) supports [Strong Customer Authentication (SCA)](https://stripe.com/en-pl/guides/strong-customer-authentication) out of the box. Remember to use S**tripe Elements** gateway with **Payment Intents** option enabled.+[Spree Stripe integration](https://github.com/spree/spree_stripe) supports [Strong Customer Authentication (SCA)](https://stripe.com/en-pl/guides/strong-customer-authentication) out of the box. We also use Stripe JavaScript SDK to render all payment forms.[Spree Braintree vzero](https://github.com/spree-contrib/spree_braintree_vzero) extension supports [3D Secure 2.0](https://developers.braintreepayments.com/guides/3d-secure/overview).diff --git a/docs/developer/security/index.mdx b/docs/developer/security/security_policy.mdxsimilarity index 86%rename from docs/developer/security/index.mdxrename to docs/developer/security/security_policy.mdxindex 28a7f64238..bdf8018692 100644--- a/docs/developer/security/index.mdx+++ b/docs/developer/security/security_policy.mdx@@ -1,5 +1,3 @@-# General guidelines-## OverviewProper application design, intelligent programming, and secure infrastructure are all essential in creating a secure e-commerce store using any software (Spree included). The Spree team has done its best to provide you with the tools to create a secure and profitable web presence, but it is up to you to take these tools and put them in good practice. We highly recommend reading and understanding the [Rails Security Guide](http://guides.rubyonrails.org/security.html).@@ -10,14 +8,11 @@ This is a list of all Spree versions currently being supported by the Spree team| Version | Release date | EOL date || ------- | ------------ | ---------- |-| 4.4 | 26.01.2022 | 26.07.2023 |-| 4.3 | 14.09.2021 | 14.03.2023 |-| 4.2 | 23.02.2021 | 23.08.2022 |+| 5.0 | 26.03.2025 | 26.03.2028 |+| 4.10 | 06.09.2024 | 06.09.2027 |If you're using an older version [please upgrade](../upgrades/). Have trouble upgrading? [Contact us for support](https://spreecommerce.org/contact/).-Or you can migrate once to [Spree as a Service](https://spreecommerce.org/spree-as-a-service/) and forget about upgrades altogether!-**Versions that aren't supported will not receive any security patches and fixes!**## Reporting Security Issuesdiff --git a/docs/mint.json b/docs/mint.jsonindex 7cfdaa089d..df83764e44 100644--- a/docs/mint.json+++ b/docs/mint.json@@ -188,6 +188,13 @@"developer/contributing/creating-an-extension"]},+ {+ "group": "Security",+ "pages": [+ "developer/security/security_policy",+ "developer/security/pci_compliance"+ ]+ },{"group": "Advanced","pages": [