Vulnerability notes, site pentests and audits
Recent vulnerabilities in plain language, and how a website pentest and a security audit work for companies.
OWASP for a small company: which site risks to close first
The Top 10 is a map of common mistakes, not an exam. For an ordinary site, access, updates, forms and other people's data matter.
Technical SEO after a redesign: how not to lose traffic
A layout change often changes addresses, speed and the index. Without a redirect map, search sees a new site on an old domain.
API security for a store and an account area: a quiet risk
The storefront can look fine while the API returns someone else's order for a swapped number.
How to choose a site contractor: questions before the contract
A portfolio shows pictures. The contract and the access show who will own the site in a year.
One password for every service: how someone else's leak opens your site
A password that already appeared in someone else's service is tried against your mail and hosting automatically.
Site development timelines: what they actually depend on
The date is missed not by layout, but by content, approvals and integrations that appeared after the estimate.
Monitoring and response: why observation matters after a report
An audit answers what was wrong on the day of the check. The site keeps changing after that.
Automation for a small company: which process to start with
Manually moving a lead from mail to a sheet and then into a CRM is a salary paid for work a plane should do.
An app review before release: what we look for in the build
A client app often stores keys, hidden addresses and a payment bypass. That is visible before publish if the build is taken apart first.
Connecting a site to a CRM: the minimal plane
A lead should create a card with a source and should not stay silent if the CRM did not answer.