PROBLEM
Tools and rules exist, but the path event → log → decision owner does not. Exposure and accounts grow faster than documentation.
PODEJŚCIE
Inventory and a hard baseline first, then visibility and control priorities. No claim that “nothing gets through”.
SCOPE
- hardening of systems and services in agreed scope
- logging, retention and an analysis path
- exposure review (ports, VPN, RDP, admin panels)
- control and gap notes
DELIVERABLE
- prioritised controls and gaps
- configuration changes or an implementable checklist
- monitoring recommendations tied to real decisions
PROCESS
- inventory of assets and access
- baseline and quick risks
- visibility (logs / alerts)
- priorities and next scope
Cybersecurity is useful when you know what you protect and how you would notice failure. I help harden systems, reduce unnecessary exposure, tidy accounts and put logging in place so an alert is a decision signal — not console noise.
Typical work covers Windows/Linux configuration review, limiting needless listeners, agreeing MFA and privileges, and a log path (Event Log, syslog, or a SIEM such as Wazuh) that remains readable after the fact. Scope is fixed before work starts: hosts, network, accounts, time and access limits.
If you need help after account takeover, fraud or a messy security debt, lawful engagement means work on your systems with your authorisation: regain control, contain damage, harden, and hand off material for deeper analysis when required. I do not bypass third-party defences or act without the owner’s written approval.
Out of scope unless agreed otherwise: a “zero trust” slide deck, around-the-clock SOC, a promise that nothing gets through. An offensive test is a separate service: Pentesting.
When the scope is one target and the price is fixed: Hygiene 48h is the file pack at 79 PLN gross, and the baseline review is one target at 349 PLN gross, express 149 PLN. A wider environment still goes through a quote.