CASE 02 — WEBSITE
Corporate Website
From domain setup to a secure launch
From “too late” to “let’s begin.”
01 — OVERVIEW
We clarify the content and functions together, launch securely, and make the site maintainable.
We separate browsing from inquiry submission, validate inputs, and control access. After launch, we keep dependencies and settings up to date.
02 — FLOW
How we work
Three stages take the site from planning and design through domain setup and launch to ongoing improvements.
- Planning and design
- Domain and launch setup
- Improvements after launch
03 — SECURITY
How we protect a site
We distinguish traffic at the entrance and combine controls for forms, admin areas, chat, and dependencies. We continue reviewing settings and updates after launch.
Distinguish traffic at the entrance
Visitors, search engines, bots, and attackers all reach a site. We check behavior and request frequency, allow useful traffic, limit excessive collection, and block attacks and spam.
- Customers
- Search engines
- AI crawlers
- Spam bots
- Attackers
Check behavior, request rates, and known attacks
Controls depend on the delivery platform and the site’s purpose.
Protect each area of the site
Forms, administration, chat, page content, and servers face different risks. Each area needs its own controls.
Select a number to inspect the area. The admin area and chat are examples when present.
Keep components updated after launch
Weaknesses may be found after a site launches. These are published examples. We check the products, versions, and configuration in use before applying the relevant fix.
2026.10.21
PHP: CVE-2026-109618
A memory-handling weakness could allow code execution under certain conditions. Check the affected versions and apply the published fix.
- Published
- Check impact
- Apply fix
2026.10.14
Next.js: image optimization
A specific SVG processing path and runtime may allow unauthenticated code execution. Check the affected configuration and update.
- Published
- Check impact
- Apply fix
2026.11.03
Next.js: mixed responses
Certain self-hosted setups may mix responses between users or expose information. Check applicability and update.
- Published
- Check impact
- Apply fix
04 — CHAT
An information chat, when useful
A site chat can answer common questions. We first define its sources and safeguards.
- 01Define the scope
Choose the public FAQs and pages the chat may use. Internal documents and personal data stay out of the search index.
- 02Answer with sources
Attach source pages so visitors can check an answer. If no answer is available, guide them to the contact form.
- 03Protect the chat entrance
Plan for attempts to redirect instructions and excessive submissions. Set retention and limits on what is sent to external AI services before launch.
- Answer only from approved sources
- Rate limits and bot checks
- Define conversation log retention
- Limit data sent externally