MIROTEC Belarus

About the website

The site covers two production areas: poultry processing and sausage packaging. A buyer can start from the production task, compare machine specifications, look at completed installations and request equipment selection.

What I did

• The equipment or page topic is filled into the enquiry automatically.
• Contact details can be filled in automatically by the browser.
• The calculator shows potential savings in money before asking for contacts, so the buyer first sees the benefit for their production and then decides whether to work together.
• The calculation result stays in view while the parameters are filled in on a phone.

Website CMS

• Built-in analytics: interest in equipment pages, traffic sources and pages per visit.
• Enquiry handling inside the panel: enquiry search, statuses, manager notes and export for working in Excel.
• Notification control: a saved enquiry stays available to the manager even if it could not be delivered to Telegram.
• Content editing: equipment, specifications, configurations, projects and expert articles.
• Checks before publishing: a preview and a test build help catch errors before the site is updated.
• Recovery after a bad edit: backups, an action log and a recoverable image bin.
• Protected admin access: signed sessions, limited login attempts, verification of editor commands and passwords stored as strong hashes.

Security

Before handing the project over to the client, an internal grey-box security audit was carried out.

Result: No critical, high or medium vulnerabilities were found in the final build of the project.

Protection against SQL and command injection

• Test: Automated parameter testing with sqlmap plus manual fuzzing of input forms.
• How it is protected: The source code never builds SQL queries by joining strings. The framework’s built-in ORM escaping is used. The application’s database access is limited to Data Reader/Writer rights, with no access to system tables.

Protection against XSS

• Test: Attempts to inject malicious JS scripts into every user text field.
• How it is protected: A strict template engine with automatic escaping of HTML entities. A strict Content Security Policy (CSP) on the web server blocks any third-party or unsafe inline code.

Component security

• Test: Software composition analysis (SCA) with Snyk and Dependency-Check.
• How it is protected: All packages are pinned to stable versions with no known vulnerabilities in the NVD database. Automatic notifications are set up for security patches to dependencies.

Admin panel isolation

• How it is protected: The admin panel is moved to a separate subdomain, hidden from search engine crawlers and protected from brute force by Fail2ban (the IP is blocked after 5 failed attempts). Signing in to the admin panel requires two-factor authentication (2FA / TOTP).

Resilience to DDoS and load

• Test: Stress testing with k6, simulating a legitimate surge of users and HTTP flood attacks.
• How it is protected: Request limits (limit_req) are set in Nginx and return error 429 when one IP exceeds them. The architecture is ready for seamless integration with external services (for example, Cloudflare / Qrator) to filter L4/L7 traffic.