Implementing security processes and tools

We build protection to fit your budget: from policies and processes to configuring security tools. Where a free open source solution covers the task, we propose it and take on its setup and support.

Security stackSample: open source and commercial solutions
  1. MonitoringWazuh, server and network logsOpen source
  2. NetworkSuricata on the perimeter, VLAN segmentationOpen source
  3. AccessKeycloak, MFA for VPN and mailOpen source
  4. VulnerabilitiesOpenVAS, monthly scansOpen source
  5. Backups3-2-1 rule, one copy offlineProcess
  6. MailSPF, DKIM, DMARC and attachment scanningConfiguration

We choose solutions for the task, the budget and your administrators

What we implement

Processes
Management of access, changes, vulnerabilities and backups.
Monitoring
Log collection and attack detection: Dozor, Wazuh, Elastic.
Network
Firewalls, segmentation, intrusion detection with Suricata and Zeek.
Access
Single sign-on, multi-factor authentication, privileged access management.
Workstations and mail
Hardening to CIS Benchmarks, mail protection with SPF, DKIM and DMARC.

Photographs

Photos: BrokenSphere, CC BY-SA 3.0; Kim Scarborough, CC BY-SA 2.0; Derrick Coetzee, CC0; Syced, CC0, Wikimedia Commons.

Approach

How we implement

  1. 01

    Assessment

    We study the infrastructure, the risks and what already works.

  2. 02

    Design

    We propose an architecture and a set of solutions with estimated costs for rollout and support.

  3. 03

    Pilot

    We test the solutions on part of the infrastructure.

  4. 04

    Rollout

    We install, configure and fit them into your processes.

  5. 05

    Handover

    Documentation, administrator training and support under contract.

What you get

  • Working security tools with documentation.
  • Documented processes: who does what and by when.
  • Trained administrators.
  • A support and update plan.
Can a free solution handle a large company’s needs?

Wazuh, Suricata and Keycloak run in large companies too. You pay for setup and support, so we compare them with commercial products on total cost of ownership.

Who will support the system after rollout?

Your administrators after training, or us under a support contract.

Can we move from open source to Dozor later?

Yes. Dozor accepts Wazuh and Elastic events, so your logs and existing work carry over.

Discuss your task

Describe the task and the timeline. We will reply, clarify the scope and propose a plan.

  1. Contract. We start with a contract and a non-disclosure agreement. The scope of work and the permissions are put in writing.
  2. Scope. Goals, systems, timing and emergency contacts are agreed before the work starts.
  3. Work. We keep you updated as the work goes and report critical findings at once.
  4. Report. We hand over a management report and a technical report with evidence and recommendations.

Or write to us: info@dozorsecurity.kz

Request: Security implementation