SECURITY OPERATIONS CENTER

Security operations center (SOC)

The Razban SOC reads the events and logs from your infrastructure around the clock, spots suspicious behavior and responds when an incident starts. It is built on 14 years of operating experience, covers more than 130 organizations and responds in under 15 minutes on average.

An analyst watching a wall of monitoring screens
Continuous monitoring
24/7
Years of operating experience
14
Organizations covered
130+
Average response time
<15′
Security operations center cycle: 24/7 monitoring, alert analysis, incident response and a monthly report. Razban SOC 24/7 monitoring Alert analysis Incident response Monthly report
Security operations center cycle: 24/7 monitoring, alert analysis, incident response and a monthly report.

SOC services

  • 24/7 monitoring

    Analysts watch security events from your infrastructure at every hour of the day.

  • Log onboarding

    Logs from servers, network devices and applications are connected, and threat-hunting rules are tuned to them.

  • Threat analysis

    Each alert is investigated to separate real incidents from false positives.

  • Incident response

    Incidents are contained, and actions follow an escalation path agreed with you in advance.

  • Monthly report

    Your security posture each month, with measurable indicators.

  • Corrective measures

    Recommendations, and their implementation, to reduce the risks the SOC uncovers.

Razban SOC capabilities

The Razban SOC rests on three pillars, SIEM, MDR and Threat hunting, and watches events from your endpoints, network and cloud services in a single view.

01

SIEM: event aggregation and correlation

Logs from servers, network devices and systems are centralized in the SIEM, and scattered events are correlated so the pattern of an attack stands out from normal activity.

02

MDR: managed detection and response

Razban analysts detect threats and act to contain them as a managed service, and the outcome of every action is coordinated with you.

03

Threat hunting

Beyond reviewing alerts, analysts actively search the collected data for signs of an intrusion that has not yet triggered an alert.

04

Endpoint, network and cloud coverage

Events from workstations and servers, network devices and your cloud services are reviewed together, so an attack can be traced as it moves between them.

05

Threat intelligence

Indicators of known threats and new attack patterns feed into the detection rules, and those rules are updated continuously.

06

Response automation

Repetitive responses to known incidents run automatically, which keeps response times short and frees analysts to focus on complex incidents.

How an incident is handled

Every security alert at the Razban SOC follows this path, from the first sign of trouble to full service recovery.

  1. Monitoring

    Events from your infrastructure are received continuously, at every hour of the day.

  2. Detection

    Detection rules and threat hunting separate suspicious behavior from normal activity, and an alert is raised.

  3. Analysis

    An analyst reviews the alert to tell a real incident from a false positive and to assess its severity.

  4. Containment

    For a real incident, containment steps are taken or reported to you according to the agreed escalation path, so the incident does not spread.

  5. Response and coordination

    The people named in the escalation path are notified, and next steps are coordinated with your IT team.

  6. Recovery and reporting

    Service recovery is followed through, corrective recommendations are made to prevent a repeat, and the incident is recorded in the monthly report.

Scope of the SOC service

What we monitor

  • Server logs
  • Network device logs
  • System and application logs
  • Websites or servers connected to the paid version of Razban Shield

What you receive

  • 24/7 monitoring of security events
  • Real incidents separated from false alarms
  • Incident containment along the agreed escalation path
  • A monthly report with measurable indicators

Suited to

  • Organizations that need security monitoring at every hour of the day
  • Teams without in-house staff for continuous monitoring
  • Websites and servers on the paid version of Razban Shield

Getting started with the SOC

  1. 1

    Log sources

    We list which servers, devices and applications will send logs.

  2. 2

    Onboarding

    The logs are connected and detection rules are tuned.

  3. 3

    Escalation path

    We agree who is called, and when, for each type of incident.

  4. 4

    Live service

    Monitoring starts, with a report every month.

Frequently asked questions

How quickly does the Razban SOC respond?

Monitoring runs at every hour of the day, and the Razban SOC responds in under 15 minutes on average.

How is a SOC different from server and network monitoring?

Monitoring tells you whether servers, networks and services are up and performing. A security operations center analyzes security events and responds to security incidents. Many organizations run both.

Does the SOC replace our IT team?

No. The SOC detects, analyzes and contains incidents, and coordinates the necessary actions with your IT team along the escalation path. Decisions about your systems stay with that team.

What does the monthly SOC report cover?

The monthly report shows the security posture of your infrastructure with measurable indicators and includes corrective recommendations to reduce the risks identified.

What do you need from us to connect to the SOC?

A list of the servers, network devices and systems to be monitored, and where their logs are kept. We review the list in the first meeting and propose how to connect each source to the SOC.

Can the SOC watch a single website?

Yes. The paid version of Razban Shield connects a website or server to Razban Cloud and puts it under SOC monitoring.

SOC consultation

Tell us about your servers, network devices and applications and where their logs are kept, and we will propose how to connect them to the SOC.

Request a Quote