Cybersecurity

What Is a Cyber Analysis Centre? Marta Security SAM as an End-to-End Threat Notification System

Marta Teknoloji•November 4, 2026•8 min read

Without a large SOC team, who is watching for security events?

Large enterprises can afford a Security Operations Centre (SOC) that watches security events around the clock. Most SMEs, municipalities, schools, hospitals and mid-sized companies are in a different position: a handful of IT staff look after user support, servers and the network all at once. Security logs pile up on servers, but nobody reads them regularly.

Attackers know this gap well. A password-guessing attack, an account quietly added to a privileged group or a security log wiped in the middle of the night all show up clearly in the event log. The problem is not a lack of records; it is that the record never reaches a person in time. Most incidents only come to light once files are encrypted or users notice something is wrong.

A cyber analysis centre exists to close that gap: collect signals from endpoints in one place, separate what matters, notify the right person and run the response on the record.

What is a cyber analysis centre, and how does it differ from a SOC?

A cyber analysis centre is the central function where security telemetry is collected, analysed and turned into alerts. A traditional SOC adds a team of shift-based analysts, an on-call rota and mature processes on top. Not every organisation needs to build a SOC, but every organisation should have a reliable answer to four questions:

  • What can we see? Which security signals are collected from servers and clients?
  • Who finds out? When something critical happens, who learns about it and through which channel?
  • Who follows it up? Who is the alert assigned to, what verdict closes it, and where are the notes kept?
  • How do we respond? How is a suspicious machine cut off from the network, and who approves it?

A well-designed threat notification system turns the answers to those four questions into software that a small team can actually run.

A threat notification system in four steps

1. Detection: never rely on a single source

No single signal source reveals every attack. An effective cyber analysis centre therefore weighs several layers together:

  • Windows and Active Directory events: brute-force attempts, account lockouts, members added to privileged groups, password resets on other users' accounts, cleared security logs and audit policy changes.
  • Endpoint behaviour: command lines launched from Office applications, suspicious PowerShell use, credential theft attempts and process injection.
  • Rule-based hunting: searching event logs for known attack traces with community-developed Sigma rules.
  • Network and lateral movement: one account logging on to many machines in a short time, internal port scanning, beaconing and DNS tunnelling.
  • Threat intelligence: matching network connections, DNS queries and installed software against known malicious address lists and catalogues of actively exploited vulnerabilities.

Mapping detections to the MITRE ATT&CK framework makes it easier to see which stage of an attack an alert belongs to: reconnaissance, credential access or lateral movement?

2. Notification: the right person, the right channel

A dashboard nobody looks at is no better than a log nobody reads. The real value of a threat notification system is putting the important event in front of a human. That requires notifications that are both multi-channel and selective:

  • Instant notification by email, SMS, Microsoft Teams, Slack and webhook,
  • Filtering by category and minimum severity,
  • Only critical alerts delivered during quiet hours,
  • Regular digests and morning reports instead of a message for every single alert.

The goal is for the team to hear about what genuinely matters straight away, without sliding into alert fatigue.

3. Case and incident management: making alerts traceable

A notification is only the beginning. Who the alert was assigned to, what was decided and why it was closed all need to be on record; otherwise the same event gets investigated twice, or not at all. Mature case management includes:

  • Status, verdict and assignee, with immutable notes and change history,
  • Related alerts grouped under a single incident, with a timeline, affected assets and root cause,
  • Tracking of mean time to acknowledge and resolve (MTTA/MTTR),
  • Alerts on critical assets automatically receiving higher priority.

Where personal data is affected, the KVKK process is part of this step too. Because personal data breaches are expected to be reported to the Turkish Personal Data Protection Board within 72 hours, it matters to track the clock from the moment of detection and to have a notification draft ready.

4. Response: fast but controlled

When a suspicious machine is found, the first job is to stop the problem spreading. Cutting the machine off from the network, killing a suspicious process or quarantining a file should not require someone to travel to site. These actions can be disruptive, though; isolating the wrong machine is an outage in its own right. That is why a four-eyes principle, requiring a second person to approve critical actions, strikes a sensible balance.

Prevention is cheaper than detection

A cyber analysis centre should not only raise alerts; it should also make the attack surface visible. Which machine has its firewall switched off, which Active Directory account is open to Kerberoasting, which server is running end-of-life software? The answers show which doors can be closed before anything happens. Hardening steps that can be rolled back also make IT teams far more comfortable changing production systems.

Who is it for?

Organisation profileCore needWhat they expect from a cyber analysis centre
SMEs and public bodies without a dedicated SOCHearing about critical eventsSelective email and SMS notifications, clear alert detail
IT teams running Active DirectorySpotting identity attacks earlyBrute-force, privilege escalation and log clearing alerts
Managed service providers (MSPs)Watching many customers from one placeA multi-tenant console isolated per customer

Questions to ask when choosing a threat notification system

  • Does it specifically recognise Active Directory attacks such as Kerberoasting, DCSync and Zerologon?
  • Can it correlate across the whole fleet, not just individual machines?
  • Can notifications be filtered by severity and time of day?
  • Can alerts be assigned as cases and closed with a verdict and notes?
  • Is remote isolation available, and can critical actions require approval?
  • Can we see the impact of suppressing a false positive before we do it?
  • Is the interface available in Turkish, and does it support KVKK processes?

Marta Security SAM: a cyber analysis centre for small teams

Marta Security SAM (Cyber Analysis Centre Management Software) is a threat detection and threat notification system developed by Marta Teknoloji. It consists of an agent installed on Windows and Linux servers and clients, and a multi-tenant web console in Turkish. It evaluates Active Directory and Windows security events, Deep Monitoring telemetry, Sigma-based Threat Hunt, lateral movement and national and international threat intelligence matches together, and maps alerts to MITRE ATT&CK.

High and critical alerts are delivered by email, SMS, Teams, Slack or webhook, with only critical ones coming through during quiet hours. Alerts become cases and incidents, with MTTA/MTTR indicators, a printable Incident Report, optional AI pre-triage and a KVKK breach notification draft with a 72-hour countdown, all on the same screen. The draft is never sent automatically, and AI suggestions are never applied automatically. One-click network isolation, process termination and quarantine are available, with optional four-eyes approval.

Rules, policies and suppression are managed in a single table under Rule Fabric, and you can preview which past alerts a suppression would affect before applying it. A 0–100 security posture score, an Active Directory attack surface audit and hardening cards that can be rolled back complete the prevention side.

You can explore every module on the Marta Security SAM product page. To arrange a demonstration for your own environment, get in touch with us.

#siber analiz merkezi#tehdit bildirim sistemi#SOC#olay müdahalesi#vaka yönetimi#KVKK#Marta Security SAM

Want to learn more?

Contact us for information about our cybersecurity, software, and infrastructure services.

Contact Us→