RU Contact us
SEC / 02 of 09 · Information security

Security you can verify, not just document

Audits, hardening and incident analysis. We prioritize by attack path, not by the length of the list.

When people call us
  • 01A 400-page scanner report and no idea what to fix first
  • 02Admins use one account everywhere
  • 03There was an incident, but nothing to reconstruct it from
  • 04Firewall rules have not been reviewed in years
+Information security: ink illustration
ADM / domain admin logged on to a workstation
LOG / logs are kept for 7 days
SEC / 02Findings are illustrative
+
Day one

What we check first

  • Map the paths from a workstation to a domain controller
  • Find where privileged credentials are left behind
  • Check log depth: what can actually be investigated
  • Compare firewall rules with real traffic
Tool

Eight baseline controls: what is in place

Tick what works in your environment today. Nothing is sent anywhere.

+
Failure patterns

Where it usually breaks

A

Privileges settle on workstations

A domain admin logs on to an ordinary PC and the credentials stay in memory. One compromised PC yields the whole domain.

B

Flat network

Users, servers and management share one segment. Any infected machine can see everything.

C

Logs nobody can use

Events are logged but kept for a week and never correlated. The attack is reported by a third party.

+
Outcome

What you keep

  • A map of attack paths to critical systems
  • A hardening plan: what to close in a day, a week, a quarter
  • Configurations and policies ready to apply
← NET

Networks

MSX →

Microsoft and Exchange

+
Contact

Describe your task

Tell us what is happening and what has been tried. The engineer who will handle it replies.