jfgamsby

Blueternal BOLT Security Toolkit (BOLT) scans your WordPress site and hosting environment for security issues, surfaces plain-English findings in wp-admin, and gives you step-by-step fix instructions for every check.
BOLT is designed for the gap between generic WordPress security plugins and full server access: it helps site owners, agencies, and hosting teams see what is actually misconfigured on the current host, which issues matter most, and which ones BOLT can safely fix from WordPress plugin context.
Free features:
<ul>
<li>31-point security scan across Server Environment, WordPress Core, Authentication, Site Exposure, Security Headers, Updates, and Writable Directories</li>
<li>Checks PHP version, MySQL version, OPcache, dangerous PHP functions, directory listing, PHP override effectiveness, loopback request health, WP-Cron health, WP_DEBUG, wp-config.php permissions, DISALLOW_FILE_EDIT, database prefix, XML-RPC, REST API exposure, application passwords, user registration, default admin username, administrator account sprawl, debug log exposure, readme.html exposure, public backup or dump artifacts, HTTPS, HSTS, core/plugin/theme updates, uploads permissions, and executable files in uploads</li>
<li>Server/PHP profile detection for Apache, Apache with PHP-FPM/FastCGI, LiteSpeed/LSAPI, Nginx with PHP-FPM, IIS, and unknown/shared-host stacks</li>
<li>“How to fix” accordion with manual instructions for every check</li>
<li>Recommendations summary of all failing and warning items</li>
<li>Host-aware action states so supported fixes show as actionable and unsupported ones stay manual</li>
<li>Dedicated Hardening tab with supported one-click hardening actions and manual priorities</li>
<li>One-click auto-fixes for WP_DEBUG, File Editor, Directory Listing, HSTS, executable files in uploads, XML-RPC, and REST API restriction when the current host supports them</li>
<li>One-click removal for public readme.html exposure and public backup, dump, environment, installer, and diagnostic artifacts</li>
<li>Persistent fix history with grouped sessions and full undo for all BOLT-applied changes, including restoring original wp-config.php and .htaccess content</li>
<li>REST public-route allowlist manager for intentional unauthenticated REST endpoints</li>
<li>Application Password Governance inventory with stale, unused, and administrator-owned API credential review</li>
<li>Attack Path Analysis: identifies realistic compromise chains based on your current configuration and shows the fastest way to break them</li>
<li>Near-Miss Detection: highlights conditions that are close to forming an attack path before they become exploitable</li>
<li>AI Security Briefing panel is visible in the Overview tab; generation and AI Settings require BOLT Pro</li>
<li>Weekly scheduled scan reports by email</li>
<li>Optional BOLT-branded PDF attachment on scheduled scan emails using dompdf when available, with a built-in plain PDF fallback</li>
<li>Reports tab status panel showing whether the BOLT WP-Cron event is registered, when it will run next, the last delivery/PDF status, and a manual test-send button</li>
<li>Email only when new issues appear</li>
<li>Alerts tab shows the Slack and generic webhook controls; delivery and test alerts require BOLT Pro</li>
<li>Activity tab with the last 7 days of security timeline entries for logins, user changes, software changes, scans, reports, alerts, and auto-fixes</li>
<li>Baseline drift detection with one active baseline, save/update/clear baseline actions, regressions since the approved scan, and finding-level before/after value diffs</li>
<li>Vulnerability Intelligence rows can show pass/fail status and CVE IDs when advisory findings are present; full advisory detail requires BOLT Pro</li>
<li>Accepted Risk Register with owner, reason, expiration date, reopen controls, and action-queue suppression for documented unresolved findings</li>
</ul>
Available through the separate BOLT Pro add-on/service (<a href="https://blueternalsolutions.com/bolt-pro" rel="nofollow ugc">learn more at blueternalsolutions.com/bolt-pro</a>):
BOLT Pro adds more coverage and less manual work through hosted checks, automation, and reporting controls.
<ul>
<li>Domain/IP reputation scan through the BOLT platform endpoint, with normalized results from Spamhaus DBL, SURBL, URIBL, Spamhaus ZEN, SpamCop, and SORBS</li>
<li>On-demand reputation re-checks from the Reputation tab</li>
<li>WordPress core file integrity monitoring against official checksums</li>
<li>Unexpected-file detection inside wp-admin and wp-includes</li>
<li>PHP malware-pattern scanning across plugins, themes, mu-plugins, and uploads, with Malware Triage Center support for hash-based expected-file decisions</li>
<li>Vulnerability intelligence for WordPress core, plugins, and themes through a configurable BOLT advisory feed</li>
<li>Full vulnerability advisory detail, including affected version range, CVSS score, and patch link when supplied by the advisory feed</li>
<li>AI Security Briefings and AI Settings</li>
<li>Daily and monthly scheduled scan cadences</li>
<li>Multiple report recipients and custom report branding</li>
<li>Slack and generic webhook alerts, including critical-only and baseline-regression-only filters</li>
<li>Full Activity timeline</li>
<li>Named baseline snapshots</li>
</ul>
<h3>External Services</h3>
BOLT only sends data to an external service when the corresponding feature is configured or explicitly used by an administrator.
<h4>Blueternal Solutions</h4>
When a site has BOLT Pro active and an administrator generates the AI Security Briefing without saving their own OpenAI API key, BOLT sends a compact, redacted JSON payload of selected fail/warn scan findings to the Blueternal Solutions BOLT API for hosted analysis. Free installs show the AI panel but cannot generate briefings. The payload can include finding labels, statuses, severities, messages, recommendations, remediation guide URLs, limited environment notes, baseline drift summaries, a payload hash, plugin version, site/home URL, and a random install identifier used for service quota. It does not send raw files, database contents, passwords, secret keys, or arbitrary page content.
The hosted AI service uses Blueternal Solutions server-side credentials and may process the redacted payload through an AI provider to return the structured briefing. The separate BOLT Pro add-on/service may also contact Blueternal Solutions endpoints for license validation, reputation checks, vulnerability intelligence, and upgrade pages. Depending on the Pro feature used, requests may include the site URL, plugin version, license key, domain, IP address, and installed WordPress core/plugin/theme version metadata needed to return the requested service response.
Service endpoint: <code>https://blueternalsolutions.com</code> 
Terms: https://blueternalsolutions.com/bolt-terms-of-service/ 
Privacy policy: https://blueternalsolutions.com/bolt-privacy-policy/
<h4>OpenAI</h4>
If BOLT Pro is active and an administrator saves an OpenAI API key in BOLT settings or defines <code>BOLT_OPENAI_API_KEY</code>, the AI Security Briefing sends the compact, redacted JSON payload directly from the site to OpenAI instead of using the hosted BOLT service. The payload can include finding labels, statuses, severities, messages, recommendations, remediation guide URLs, limited environment notes, and baseline drift summaries. It does not send raw files, database contents, passwords, secret keys, or arbitrary page content.
Service endpoint: <code>https://api.openai.com</code> 
Terms: https://openai.com/policies/terms-of-use/ 
Privacy policy: https://openai.com/policies/privacy-policy/
<h4>Google Safe Browsing</h4>
If BOLT Pro is active and an administrator saves a Google Safe Browsing API key, the Browser Blocklist reputation check sends the site’s home URL and domain URL to the Google Safe Browsing Lookup API v4 when a reputation check runs. This is used only to determine whether the site is flagged for malware, phishing, unwanted software, or potentially harmful applications. The request also includes the saved API key, a BOLT client identifier, and the plugin version. BOLT does not send scan findings, files, database contents, passwords, license keys, or arbitrary page content to Google Safe Browsing.
Service endpoint: <code>https://safebrowsing.googleapis.com/v4/threatMatches:find</code> 
Terms: https://developers.google.com/terms 
Privacy policy: https://policies.google.com/privacy
<h4>Slack</h4>
If BOLT Pro is active and an administrator saves a Slack incoming webhook URL in BOLT Alerts, scheduled alerts or the manual test alert send alert text to the configured Slack webhook. The payload can include the site name, site URL, BOLT admin URL, scan score, score label, score delta, baseline score delta, issue count, issue labels, issue severities, issue statuses, issue messages, baseline drift summaries, capture time, and whether the alert is a test. It does not send raw files, database contents, passwords, secret keys, license keys, or arbitrary page content.
Service endpoint: the Slack incoming webhook URL configured by the administrator, usually <code>https://hooks.slack.com/services/...</code> 
Webhook documentation: https://api.slack.com/incoming-webhooks 
Terms: https://slack.com/terms-of-service/api 
Privacy policy: https://slack.com/privacy-policy
<h4>Generic Webhook</h4>
If BOLT Pro is active and an administrator saves a generic webhook URL in BOLT Alerts, scheduled alerts or the manual test alert send a JSON alert payload to the exact URL configured by that administrator. The payload can include the site name, site URL, BOLT admin URL, scan score, score label, score delta, critical-only and baseline-only alert flags, baseline score delta, issue count, issue labels, issue severities, issue statuses, issue messages, recommendations, baseline drift summaries, capture time, and whether the alert is a test. It does not send raw files, database contents, passwords, secret keys, license keys, or arbitrary page content.
Service endpoint: the generic webhook URL configured by the administrator. 
Terms and privacy policy: determined by the administrator-configured destination service.

Blueternal BOLT Security Toolkit

WordPress and hosting security scanner with plain-English findings, safe hardening actions, reports, and Pro AI summaries.

shasha310

Harden your web applications.
HTTP header fields are components of the header section of request and response messages. The headers define the operating parameters of an HTTP transaction.
Securing HTTP headers will improve the resilience of your web application against many common attacks including those that are on the OWASP top 10 list.
Securing headers can also improve your SEO rank and in addition to preventing websites from being marked as dangerous by browsers and antivirus applications.
Protect sensitive user information and be compliant with privacy regulations. Defend users from stealing private data by protecting website cookies. Use the proper directive such as “secure”, “httponly” and “samesite”, all of those will be applied automatically by “Secure HTTP Headers” plugin.
Secure HTTP Headers will automatically analyze any website and will build up secure headers directives, by the latest best practice.
In addition, Secure HTTP Headers offers fully configurable options, apply or skip any header directive as needed.
Install and activate Secure HTTP Headers with full confidence, the deactivation of this plugin will return your website header directives to their original state.
<h3>Main plugin functionality</h3>
<ol>
<li>
HTTP Strict Transport Security – helps to protect websites against man-in-the-middle attacks and cookie hijacking
</li>
<li>
X-Frame-Options – helps to protect users against ClickJacking attacks
</li>
<li>
X-Content-Type-Options – helps to prevent the browser from MIME-sniffing
</li>
<li>
Referrer-Policy – helps to control how much referrer information should be included with requests
</li>
<li>
Clear-Site-Data – helps to ensure that data is deleted from the browser if the user logs out
</li>
<li>
X-Download-Options – helps to control how IE 8 will handle downloaded HTML files
</li>
<li>
Access-Control-Allow-Origin – helps to ensure whether the response can be shared with requesting code from the given origin
</li>
<li>
Cross-Origin-Embedder-Policy – helps to prevent a document from loading any cross-origin resources that don’t explicitly grant the document permission
</li>
<li>
Permissions-Policy – helps to allow and deny the use of browser features in its own frame, and in content within any iframe elements in the document
</li>
<li>
Cross-Origin-Opener-Policy – helps to protect websites against a set of cross-origin attacks dubbed XS-Leaks
</li>
<li>
Cross-Origin-Resource-Policy – helps to protect websites against speculative side-channel attacks, like Spectre, as well as Cross-Site Script Inclusion attacks
</li>
<li>
X-Permitted-Cross-Domain-Policies – helps to control how cross-domain requests from Flash and PDF documents are handled
</li>
<li>
Cookie Http-Only flag – helps to protect websites against Cross-Site Scripting, or XSS attacks
</li>
<li>
Cookie Secure flag – helps to ensure that cookie is sent over a secure connection
</li>
<li>
Cookie Samesite Lax flag – helps to protect websites against CSRF and XSSI attacks
</li>
<li>
Expect-CT – helps to prevent the use of misissued certificates for a website. Note: The Expect-CT will likely become obsolete in June 2021
</li>
</ol>
<h3>What are the optional extras?</h3>
Magnisec is offering “Secure HTTP Headers enhanced”
A plugin that contains, in addition, an engine that watches and builds in any website changes a CSP – Content Security Policy that is best practice and recommended by all professional securities experts, that mitigate XSS -Cross site Scripting, one of the most common and destructive attacks.
Price: 50$ /year for a domain.
More details and installation <a href="https://magnisec.com" rel="nofollow ugc">here</a>

Secure HTTP Headers

Secure HTTP headers - Essential, and easy.

Blueternal BOLT Security Toolkit vs Secure HTTP Headers