Vulnerability notes, site pentests and audits
Recent vulnerabilities in plain language, and how a website pentest and a security audit work for companies.
A personal data policy: which sections it needs
A template from the internet almost always describes someone else's company. Below is the shape that has to match your form.
Consent on a lead form: how not to hide it in the footer
A box saying "I agree with everything" next to a policy on another site proves little. Purpose, wording and a real choice matter.
Security from the first mockup, not as a slide before release
Code appears faster than anyone can review it. Access and trust boundaries are cheaper to discuss on the mockup.
Site speed and SEO: what to measure besides a pretty score
A score of 90 in a tool and five seconds on a customer's phone live together quite happily. Field data and page weight are what to look at.
HTTPS and the browser lock: what it actually means
The lock says the connection to this domain is encrypted. It does not say the site is safe or the form is honest.
A CMS update without downtime: an order, not a button
An Update button on the live site bets the layout and the leads on a stake nobody agreed to.
Why a website pentest before launch is cheaper than after
A release without a logic review leaves holes where a storefront scanner stays quiet: other people's orders, roles and APIs.
A custom site or a website builder: when to use which
A builder checks a hypothesis faster. A custom site is needed when an account area, a catalog and access requirements appear.
An employee phish: what to do in the first hour
The mail is already open, or the password is already typed in. The order of actions matters more than finding someone to blame.
The site dies during an ad campaign: growth or an attack
Ads are on, traffic exists, the server chokes. How to tell a successful campaign from bots without buying every shield at once.