Available now
All prices net plus VAT.
Download the free Plugin Suite and install it in the admin, without SSH. Through it you install the Security Center and get every update with one click.
How to start the first check, read and fix findings, protect the login with a second factor and a country block, use the change log, and what the plugin stores.
The Security Center regularly checks your shop for skimmers, malware, changed files, weak accesses, critical changes to settings and known vulnerabilities. Every anomaly is stored as a finding with a level, an explanation and steps to fix it.
In addition, the plugin protects the administration login: with two-factor login, a country block, a list of allowed addresses, a login log and a log of all critical changes.
A check, not a promise of protection: the check reports anomalies and changes. It does not prevent an attack and does not find every piece of malware. Every finding should be reviewed before it is confirmed.
Shopware 6.6 and 6.7: the plugin runs on both versions, in German and English, with dark mode. Up to version 1.5 it was called Security Scanner.
The licence is assigned via the Plugin Suite and checked automatically on first opening. Without a valid licence the plugin shows the licence view where you enter the key. Without a licence no check runs and the login protection does not apply: nobody is locked out by an expired licence.
During the first check the plugin remembers a checksum for every file and the current value of critical settings. That is the initial state. From the second check on, every deviation is reported: new, changed and deleted files, new administrators, changed payment methods.
The initial state should be clean. If you suspect the shop has already been changed, first look at the findings of the malware and original comparison areas, which work without an initial state.
Under Settings, Directories the initial state can be discarded with Record again, for example after a server move.
The overview shows the security score from 0 to 100, the open findings by level, the last check and the number of files checked. The score drops with every open finding, more so for high levels. Confirmed and resolved findings do not count.
Recommended setup lists the protective features that are not set up yet. Switch on activates a feature immediately, Set up takes you to the right place. Hide whatever this shop does not need.
Score history shows the score at the end of the most recent checks, 30 at most. The curve starts with the second check and is also part of the PDF report.
Below are the foreign scripts of the storefront, the latest administration logins, the quarantine and the latest checks. PDF report downloads the current state as a PDF.
Every finding has a level: High needs attention immediately, Medium should be reviewed soon, Low is a weakness without acute danger, Notice is for information.
Details shows what was found, the recommendation and all data on the finding. If the finding is fine, click Confirm. It then counts as reviewed and only comes back when something changes. Once the cause is removed, the next check closes the finding on its own.
After a Shopware or plugin update many files change. Confirm all file changes accepts them in one step. Several findings can be confirmed together via the selection.
The details of a finding list numbered steps to fix it. The same steps appear in the e-mail and in the PDF report.
For vulnerabilities the plugin distinguishes where the affected package comes from: Shopware itself, a package Shopware ships, a plugin or your own project. That decides whether a Shopware update, a plugin update or a command such as composer update helps. The command is in the finding, ready to copy.
Several vulnerabilities with the same cause are grouped into one finding, for example all Symfony packages that one Shopware update fixes together.
For findings on files the details offer these tools:
Files under vendor, config and bin cannot be quarantined, so the shop does not break. Restoring the original helps here.
For findings on accesses the matching measures are right in the finding: Lock user logs the user out everywhere and deactivates them, Lock integration withdraws the access, Deactivate payment method removes it from the checkout. You cannot lock your own user.
If the view from outside reports missing headers, the finding offers the button Set headers now. You get the same under Settings, Storefront protection. On every page the plugin only adds what is missing: protection against wrong type detection, protection against embedding in foreign pages, a referrer policy and, over https, the instruction to open the shop encrypted only. Whatever Shopware or the server already sets remains untouched.
Under Settings, AI interface you store provider, key and model and check the connection with Test connection. After that the details of a finding offer the AI assessment button. The AI rates the finding as harmless, worth checking or critical and names steps. The assessment is a second opinion, not a decision.
Only the data of that one finding is sent, plus an excerpt for files. If the AI Product Advisor is installed, its key is used as well.
From then on the administration login page asks for the code after user name and password. The password is checked first, then the code. After five wrong codes the login is locked for 15 minutes. Integrations with an API key keep logging in without a code.
Under Settings, Logins switch on Login only from allowed addresses and enter one IP address or network per line, for example 203.0.113.10 or 203.0.113.0/24. IPv6 is supported.
When saving, the plugin checks whether your current address is in the list. If not, nothing is saved. A list that is switched on but empty locks nobody out.
Under Settings, Logins switch on Restrict login by country, choose the mode (allow only these countries or block these countries) and add the countries. The block only applies to logging in to the administration with user name and password, not to the storefront and not to integrations.
When saving, the plugin checks whether your own country would still be allowed. An address from the list of allowed addresses may log in regardless of the country.
The mapping of addresses to countries comes from DB-IP (db-ip.com, licence CC BY 4.0). The plugin downloads the data to your server once a month and looks it up there. It is not accurate in every case: VPN and mobile networks abroad may differ. Behind a proxy or CDN Shopware must know the real address of the visitor, the Login protection tab points this out.
On the server in the shop directory this command removes the second factor for all users and switches off the address list and the country block:
bin/console staw:security:login-reset
With a user name after it, it only applies to that user. Without console access an empty file is enough:
var/staw-security-scan/disable-login-protection
As long as the file exists, code, address list and country block are suspended.
The plugin logs successful and failed administration logins with user and address. Ten failed attempts from one address within 15 minutes and a login from a previously unknown network are reported as findings. Entries are deleted after the configured number of days.
The Login protection tab shows the number of open sessions per user. Log out everywhere ends all sessions of that user, for example after a lost device.
An administrator who has not logged in for longer than the configured number of days is reported as a finding. Counting starts from the moment the plugin began observing logins. The default is 180 days, 0 switches the report off.
With Match new passwords against data leaks switched on, the plugin checks every newly set admin password against the collection of known data leaks of Have I Been Pwned. The first five characters of a checksum of the password are transmitted, the comparison itself happens on your server. The password and the full checksum do not leave the server.
If the password appears in a data leak, a finding of level High is created. It closes as soon as the user sets a different password. The default is off because a third-party service is involved.
The Log tab shows who changed what and when: users, roles, integrations, payment and shipping methods, domains, flows, webhooks, plugins and settings. Every entry names time, user or integration, address, the affected entry and the names of the changed fields. The content of the fields is not stored.
Entries are deleted after the configured number of days, the default is 90 days. The log can be switched off under Settings, Logins.
Automated attack tools look for pages that do not exist in a Shopware shop, such as /wp-admin or /phpmyadmin. With traps switched on, the plugin blocks such an address for the configured time, the default is 60 minutes. The Login protection tab lists the blocked addresses and lifts a block on request.
The traps apply to addresses the web server passes on to Shopware. Requests for .php files or files such as /.env are answered by the web server itself on many servers and then never reach the plugin. Behind a proxy or CDN Shopware must know the real address of the visitor, otherwise the block would hit the proxy.
A Content Security Policy tells the browser which addresses it may load scripts from. An injected skimmer from a foreign address is then not executed.
The default is Off. Test the checkout with all payment methods before enforcing.
After every check the plugin reports new findings from the chosen level by e-mail, including the steps to fix them. Every finding is reported once. With Report resolved findings switched on, the next report also names what has been resolved since the last one.
In addition a webhook can be entered, for example for Slack or Microsoft Teams, and a weekly summary with the state of all open findings. Both can be checked with a test message.
The PDF report in the overview summarises the score, its history, open findings with steps and the latest checks. Under Settings, Report by e-mail you store your own sender name and logo, for example as an agency for your clients. Times are shown in the user's time zone.
The full check runs on a schedule via Shopware's scheduled tasks, by default daily at 3 am. The most reliable setup is a cron job on the server that runs the scheduled tasks and the message queue.
Check without cron job: if the scheduled tasks do not start the check, the plugin runs it itself. This starts no earlier than three hours after the due time, as soon as someone opens the shop or the administration, and runs in short sections after the page has been delivered. The configured hour does not apply in this case. The overview points this out, and the list of checks says Without cron job. It can be switched off under Settings, Schedule.
Self-monitoring: if no check runs for two days anyway, for example because the shop has no visitors, the overview warns and one e-mail is sent.
The instant check reacts to critical changes: new administrators, integrations, plugins and changed payment methods are checked and reported seconds later.
All data lives in the database and in the directory var/staw-security-scan of your shop. Personal data here mainly means IP addresses and user names of administrators:
Only these requests go out:
Legal basis: the logs serve the security of the shop, which is usually a legitimate interest under Art. 6(1)(f) GDPR. Administrators are affected and, for the traps, visitors as well. Add the processing to your record of processing activities.
Suggested text for the privacy policy if the traps are switched on:
To protect our shop against automated attacks we detect requests that specifically look for vulnerabilities. In this case we store the IP address of the requester for up to 60 minutes and block access for that time. The legal basis is our legitimate interest in the security of our service (Art. 6(1)(f) GDPR). The data is not passed on to third parties.
For administrators a note in the internal documentation or in the contract with the agency is usually enough. The text is a suggestion and not legal advice, adjust the duration to your setting.
The scanner runs inside the shop itself. An attacker with full access to the server can switch it off or bypass it. It does not replace a firewall, updates or backups. Malware that follows no known pattern and was present before the first check can remain undetected unless it sits in the Shopware core.
The plugin is visible to users who may manage extensions. Such a user sets up two-factor login for themselves and for others.
When uninstalling with the option to delete all data, the plugin removes its tables and settings, including the login log and the change log. Second factor, address list and country block then no longer apply for any user. Only files in quarantine remain under var/staw-security-scan/quarantine and can be deleted by hand.
Questions, bugs or wishes: reach us directly via Request a feature in the plugin or the contact form.
Every finding type with meaning and recommendation, exactly as shown in the plugin.
This file did not exist during the last check and does not belong to a plugin whose version has changed.
Recommendation: Check whether the file comes from your own update or deployment. If not: back up the file, remove it and review the accesses.
The content of this file differs from the recorded initial state although neither the plugin version nor the Shopware version has changed.
Recommendation: Compare the change with the original. Unexpected changes in the Shopware core or in plugins are a strong warning sign.
This file existed in the initial state and is now missing.
Recommendation: Check whether the file was removed on purpose.
Media and file folders normally contain only images and documents. Script files there are a typical sign of a backdoor.
Recommendation: Back up the file and remove it. Then find out how it could be uploaded.
This file is located in the publicly reachable directory and can be downloaded from outside.
Recommendation: Remove the file from the public directory.
The file contains code as it occurs in backdoors and skimmers.
Recommendation: Look at the excerpt and the file. Some plugins use similar techniques for harmless purposes, ask the manufacturer if in doubt.
A database content loads a script from an address that is not allowed.
Recommendation: Check whether the script was added on purpose. If so, allow the address, otherwise clean the content.
A database content contains obfuscated script code. Skimmers are often injected this way.
Recommendation: Review and clean the content immediately, then check the administration accesses.
A script in a database content accesses payment fields and sends data.
Recommendation: Review and clean the content immediately, then check the administration accesses.
The storefront loads a script from an address that is not on the list of allowed addresses.
Recommendation: If the address belongs to a service you use, allow it. Otherwise find out which plugin or content includes the script.
A storefront page contains obfuscated script code.
Recommendation: Review the page source and look for the origin of the script: theme, plugin or content.
An embedded script accesses payment fields and sends data.
Recommendation: Review the page source. If the script does not come from the payment provider, remove it immediately.
A user for the administration has been created since the last check.
Recommendation: If the user is known, confirm. Otherwise delete it immediately and change all passwords.
An existing user has received full administrator rights since the last check.
Recommendation: Check who granted the rights.
A new API access has been created since the last check.
Recommendation: If the integration is known, confirm. Otherwise delete it.
A new API access key has been created for a user.
Recommendation: Check whether the key is needed.
A payment method has been created since the last check. Fake payment methods redirect customers to foreign accounts.
Recommendation: Look at the payment method in the settings. If it is unknown, deactivate and delete it.
A plugin has been installed since the last check.
Recommendation: If the plugin is known, confirm.
An app has been installed since the last check.
Recommendation: If the app is known, confirm.
The environment is not set to production or debug mode is on. Error pages then show internal details.
Recommendation: Set APP_ENV to prod in the .env file.
This file is located in the public directory and can reveal credentials or internal information.
Recommendation: Remove the file. If it contained credentials, change them.
The Shopware installer or update file is still in the public directory.
Recommendation: Delete the file if no update is currently running.
The entry file of the shop can be changed by any user of the server.
Recommendation: Set the file permissions to 644.
The image contains script code. If it is opened directly in the browser, the code runs in the name of the shop.
Recommendation: Look at the image and replace it with a cleaned version. Remove it if it comes from an unknown source.
A storefront form sends its input to an address that does not belong to the shop and is not allowed.
Recommendation: Check whether the form belongs to a service you use, such as newsletter or payment. If so, allow the address, otherwise look for the origin in the theme, plugin or content.
The storefront invisibly embeds a page from a foreign address. This is used to track visitors unnoticed or to capture input.
Recommendation: If the address belongs to a service you use, allow it. Otherwise find the origin and remove it.
The value APP_SECRET is very short or a known placeholder. It secures sessions and logins.
Recommendation: Set a random value of at least 32 characters in the .env file. All users have to log in again afterwards.
The newly set password of this user appears in published data leaks. Attackers try such passwords first.
Recommendation: Set a new password that is not used anywhere else and set up two-factor login.
This administrator has not logged in for the configured number of days. Unused accesses with full rights are an unnecessary risk.
Recommendation: Check whether the access is still needed. If not, lock or delete the user.
Vulnerabilities have been publicly reported for several installed packages of the same origin. One update fixes them all at once.
Recommendation: Update the packages together.
Vulnerabilities have been publicly reported for the installed version of this package.
Recommendation: Update the package to at least the version named. Symfony and Shopware packages arrive with the next Shopware update. For Shopware, the current security plugin closes many vulnerabilities without an update, in that case the finding can be confirmed.
Vulnerabilities are no longer fixed for this PHP version.
Recommendation: Switch to a current PHP version supported by Shopware at your hosting provider.
Security updates for this PHP version end in less than 90 days.
Recommendation: Plan the switch to a newer PHP version.
A newer version of this plugin is available. Updates often contain security fixes.
Recommendation: Look at the changes of the update and update the plugin.
The password of this user is on a list of common passwords or can be derived from the user name, e-mail address or shop name. The password itself is not stored or shown.
Recommendation: Change the password immediately. Use a long, random password from a password manager.
This user name is the first one tried in attacks.
Recommendation: Create a user with an individual name and remove or rename this account.
The password of this user is older than the configured threshold.
Recommendation: Change the password, especially if it was used by several people or former service providers.
The administration allows passwords with fewer than 12 characters.
Recommendation: Set the minimum length to 12 or more under Settings, Users and permissions.
Customers can register with a password of fewer than 8 characters.
Recommendation: Set the minimum length to 8 or more under Settings, Login and registration.
This API access may do everything an administrator may do. If the key falls into the wrong hands, the entire shop is affected.
Recommendation: Assign the integration a role with exactly the rights it needs. If it is set up like this on purpose, confirm the finding.
This access key has not been used for longer than the configured threshold.
Recommendation: Delete integrations and keys that are no longer needed.
When fetched from outside, this address returns the content of a file that contains credentials or internal information.
Recommendation: Remove the file or block access on the server. If it contained credentials, change them immediately.
The server shows a list of all files for this directory.
Recommendation: Switch off directory listing in the server configuration.
The home page is delivered without some headers that protect browsers against embedding, wrong content detection or unencrypted requests.
Recommendation: Add the missing headers in the server configuration or at your hosting provider.
The shop can be reached via http without redirecting to https. Login data can be transmitted unencrypted this way.
Recommendation: Set up a redirect from http to https on the server.
This domain is stored in the sales channel with http instead of https.
Recommendation: Set up a certificate and switch the domain in the sales channel to https.
The certificate of this domain has expired. Browsers warn visitors about the shop.
Recommendation: Renew the certificate immediately.
The certificate of this domain expires in less than 14 days.
Recommendation: Check whether the automatic renewal works, otherwise renew the certificate.
A domain has been added to a sales channel since the last check.
Recommendation: If the domain is known, confirm. Otherwise remove it and review the administration accesses.
The address of a domain has been changed since the last check.
Recommendation: Check whether the change was intended.
An existing payment method is now processed by different code than during the last check. Payments can be redirected this way.
Recommendation: Check immediately whether an update of the payment plugin is the reason. If not, deactivate the payment method and review the accesses.
Server, sender or delivery address for e-mails of the shop have been changed. Order confirmations and password mails can be read this way.
Recommendation: Check whether the change was intended. If so, confirm.
An ID for tag manager, analytics or pixel has been set or changed. A foreign ID can be used to load arbitrary code into the shop.
Recommendation: Compare the ID with your own account at the provider. If it matches, confirm.
The ID for Google Analytics in the sales channel has been set or changed.
Recommendation: Compare the ID with your own account. If it matches, confirm.
The shop now sends events such as orders or customer data to an additional address.
Recommendation: If the address belongs to an installed app, confirm. Otherwise remove the webhook.
An action in the Flow Builder sends e-mails to fixed recipients or data to a foreign address. The target is new or has been changed.
Recommendation: Look at the flow in the Flow Builder. If the target is known, confirm.
A role may now change users, integrations, plugins, payment methods or system settings.
Recommendation: Check who granted the rights and whether all users of this role need them.
The e-mail address of an administration user has been changed. An account can be taken over this way via the forgotten password function.
Recommendation: Ask the user whether they changed the address themselves.
A user has logged in from a network from which they were not known before.
Recommendation: Ask the user. If it was not them, lock the user and change the password.
There were at least ten failed logins from one address within 15 minutes.
Recommendation: Block the address on the server or in the firewall and check whether the affected users have strong passwords.
For the domain the shop sends e-mails with, it is not defined which servers may send in its name. This makes it easier for others to forge e-mails in the name of the shop.
Recommendation: Create an SPF record at the provider of the domain.
For the sender domain it is not defined how recipients should handle forged e-mails.
Recommendation: Create a DMARC record at the provider of the domain, initially with p=quarantine.
The DMARC record is set to p=none. Forged e-mails are only reported this way, not rejected.
Recommendation: After reviewing the reports, switch to p=quarantine or p=reject.
This file of the Shopware core does not match the published state of the installed version. This is also noticed if the file was already changed before the first check.
Recommendation: Compare with the original. If the change does not come from a deliberate patch, restore the file from the original package and review the accesses.
This file is located in the directory of the Shopware core but does not belong to the installed version.
Recommendation: Look at the file. If it does not belong to a deliberate patch, back it up and remove it.
An unusually high number of payments failed or were cancelled in the last 24 hours. This is how fraudsters test stolen card data.
Recommendation: Check orders and the payment provider. If possible, activate a captcha or the fraud protection of the payment provider.
Far more customer accounts than usual were created in the last 24 hours.
Recommendation: Look at the new accounts. In case of bots, switch on captcha and double opt-in for the registration.
A new customer password was requested noticeably often in the last 24 hours. This can be an attempt to take over customer accounts or to flood mailboxes.
Recommendation: Check whether the requests come from a few addresses and block them.
A noticeably high number of orders came from a single address within 24 hours.
Recommendation: Look at the orders. This can be normal for business customers or marketplaces, in that case confirm.
This administrator logs in with a password only while other users already use a second factor.
Recommendation: Set up two-factor login for the user in the Login protection tab.
The settings live in the Settings tab, collapsed by area. The search field finds every option directly.
Defines whether and how often the shop is checked automatically. The check runs via the scheduled tasks of Shopware.
Checks the shop regularly in the background.
Checks accesses and critical settings at the moment they are changed in the administration and reports new findings directly instead of at the next scheduled check.
How often the automatic check runs.
Hour in server time at which daily and weekly checks start.
If the scheduled tasks of Shopware do not start the check, for example because the cron job or worker is missing, the plugin runs it itself after a page request. This happens in short sections after the page has been delivered and starts no earlier than three hours after the due time. The configured hour does not apply in this case.
Number of checks kept in the overview.
Which areas are checked. Each check can be switched off individually.
Compares files of plugins, apps and custom code with the recorded initial state.
Includes the files under vendor/shopware in the file comparison.
Compares the files of the Shopware core with the published state of the installed version. For this, a directory is loaded from GitHub once per version. Requires the comparison of the Shopware core.
Searches files for code as it occurs in backdoors and skimmers, including the compiled theme.
Reports executable files in media and file folders as well as SVG images with script.
Searches settings, shopping experiences, product and category texts, snippets and mail templates for scripts.
Reports new administration users, integrations, access keys, payment methods, plugins and apps.
Checks production mode, critical files in the public directory, file permissions and the secret key of the shop.
Fetches home page, cart and login of every domain and reports third-party scripts, forms with a foreign target and invisible frames.
Records domains, processing of payment methods, e-mail delivery, tracking IDs, webhooks, flow targets, rights of roles and e-mail addresses of users and reports every change.
Tests administration accounts against common and derivable passwords and reports old passwords, default names as well as far-reaching and unused API accesses. Passwords are not stored.
Matches Shopware, PHP and public packages against reported vulnerabilities and shows plugin updates. For this, the names of the public packages are sent to packagist.org.
Fetches your own domains via the internet and reports reachable files with credentials, backups, missing encryption, missing headers and expiring certificates.
Reports conspicuous clusters of the last 24 hours: failed payments, registrations, password requests and orders from one address.
From when old passwords, unused API accesses and clusters in the shop are reported.
Passwords of administration users that are older are reported. 0 switches the report off.
Integrations and access keys that have not been used for this long are reported. 0 switches the report off.
From this number of failed or cancelled payments within 24 hours a finding is created. 0 switches the report off.
From this number of new customer accounts within 24 hours a finding is created if it is also far above the usual. 0 switches the report off.
From this number of requested customer passwords within 24 hours a finding is created. 0 switches the report off.
From this number of orders from a single address within 24 hours a finding is created. 0 switches the report off.
Security headers, the Content Security Policy for scripts and forms, and traps that lock out attack tools.
The plugin sets the headers that are missing on every page: protection against wrong type detection, protection against embedding in foreign pages and a referrer policy. Whatever Shopware or the server already sets remains untouched.
Browsers then only call the shop encrypted for 180 days. Only switch on if the shop permanently runs over https. Only works together with the switch above.
Off: no policy. Report only: nothing is blocked, browsers report addresses that are not allowed. Enforce: scripts, frames and form targets of foreign addresses are blocked. Let it report for a few days and review the list in the overview before enforcing. Inline scripts remain allowed.
Whoever requests addresses such as /wp-login.php or /.env, which do not exist in a Shopware shop, is blocked for the configured time. This applies to addresses the web server passes on to Shopware, for example /wp-admin or /phpmyadmin. Behind a proxy or CDN without TRUSTED_PROXIES the plugin blocks nobody.
An address that walked into a trap stays blocked for this long. A block can be lifted early in the Login protection tab.
Log of the logins to the administration and restriction to allowed addresses.
Stores time, user name, IP address and result of every login to the administration. Passwords are not stored.
Older log entries are deleted at the next check.
Administrators who have not logged in for this long are reported as a finding. Counting only starts once the plugin itself has been observing for that long. 0 switches the check off.
When an admin password is set, the plugin checks whether it appears in published data leaks (Have I Been Pwned). Only the first five characters of a checksum leave the server, never the password.
Records who changes users, roles, payment methods, domains and settings. Visible in the Log tab.
Older entries of the change log are deleted.
Logging in to the administration with user name and password is only possible from the listed addresses. Integrations and running sessions remain unaffected.
One address or network per line, for example 203.0.113.10 or 203.0.113.0/24. Your own current address is shown in the Login protection tab.
Logging in to the administration with user name and password is allowed or blocked by the country of the address. Integrations and running sessions remain unaffected. Addresses on the list of allowed addresses apply regardless of country.
Allow only the selected countries or block the selected countries. If the country of an address cannot be determined, it is not blocked.
Select countries for the login, for example Germany, Austria and Switzerland. Clicking a country removes it again.
The mapping of addresses to countries comes from DB-IP (db-ip.com, licence CC BY 4.0) and is loaded monthly by the server. It is not accurate in every case, VPN and mobile networks abroad may differ.
Access to the language model for assessing findings. The file path and an excerpt of the code are sent to the selected provider.
Which company provides the language model. The selection determines which models are available.
Key from your account at the provider. If the field stays empty, an existing key of the AI Product Advisor is used.
The fast default model is sufficient for assessing findings.
Checks key and model with a short request, even without saving first.
Additional directories for the file comparison and directories that are skipped.
One directory per line, relative to the shop directory, for example vendor/store.shopware.com.
One directory per line. Files below are not checked.
Discards the recorded state of all files. The next check records it again, open file findings are closed.
Addresses from which scripts and frames may be loaded and to which forms may send without creating a finding.
One address per line, without https. Subdomains are included.
New findings are reported by e-mail after every check.
Sends an e-mail after a check if there are new findings.
Leave empty to use the e-mail address from the basic information of the shop.
Findings below this level only appear in the administration.
Sends a test message to the recipient.
Sends a summary with score and open findings once a week.
If a reported finding has disappeared in a later check, the next report says so.
Name in the header of the PDF report, for example that of your agency. Empty means Stone & Water.
Own logo for the header of the PDF report, as JPEG or PNG up to 1 MB. The image is shown on a white background.
Address of an incoming webhook, for example from Slack or Teams. New findings are additionally sent there. https only.
Saves the settings and sends a test message to the webhook.
All prices net plus VAT.
Download the free Plugin Suite and install it in the admin, without SSH. Through it you install the Security Center and get every update with one click.
An edition for the Shopware Community Store is planned. Until then the plugin is available directly from us, with the full feature set.