CUBRA Entry Swarm

Protection against DDoS attacks – our own technology in the node (switching entry points under attack — in development)

Product class: DDoS protection at layers L3–L7 – network, transport and application

A DDoS attack floods a server with millions of requests until it stops responding to its own users. Our technology filters out unwanted requests before any costly processing, and under attack it changes the entry points – so your people keep working.

How it works

DDoS protection without third-party services

Protection is built into the CUBRA Node. You do not need to hand your traffic over to someone else’s cloud to have it cleaned.

Filtering before processing

A request without the right admission is dropped immediately, without using the node’s memory or processor.

Entry points change (in development)

Under attack, the node moves your people to new entry points, while the attackers keep hitting places where nobody is left (switching entry points under attack — in development).

Your people – unhindered

CUBRA apps know where to connect and switch over on their own, with no human involvement.

Data does not go outside

Traffic does not pass through third-party scrubbing centres – messages and metadata stay in your network.

Together with network protection

In CUBRA Shield, DDoS protection works together with the firewall, intrusion prevention and website filter.

Reports in one panel

Attack events and node status are in CUBRA Console, and alerts go to the duty officer’s phone.

Who needs it

When a service outage is costly

  • Government bodies and critical infrastructure
  • Banks, payment services and retail
  • Telecom operators and data centres
  • Media and civil society organisations under pressure
Honest about the limits

What depends on the line

If an attack completely saturates your provider’s line, no node inside the network can change that. For such cases, we plan backup lines and entry points in different networks together with you.

In detail

How protection works under attack

On an ordinary day, the CUBRA Node accepts connections from your people and services just like any server. The difference is that every request must present the right admission before the node spends any memory or processor time on it. A request without admission is dropped immediately, so millions of unwanted requests cost the node almost nothing.

If the attack intensifies, the node moves your people to new entry points. CUBRA apps know where to connect and switch over on their own – people notice at most a short pause. Meanwhile, the attackers keep hitting places where nobody is left. Attack events and node status are visible in CUBRA Console, and an alert goes to the duty officer’s phone (switching entry points under attack — in development).

Comparison with a typical traffic scrubbing service

  • Typical service: all your traffic passes through someone else’s infrastructure. CUBRA: protection in your own node, and traffic does not leave your network.
  • Typical service: sees all your requests and metadata. CUBRA: nothing goes to third parties, and message content is encrypted anyway.
  • Typical service: a separate contract and a separate panel. CUBRA: protection in every form of node, managed in the same CUBRA Console.
  • Typical service: handles very large attacks on the line well. CUBRA: for such cases, we plan backup lines and entry points in different networks together with you.

Who needs it most

Banks and payment services, where an hour of downtime means lost payments and customer complaints. Government bodies that are attacked in waves during events of public importance. Telecom operators and data centres responsible for the availability of their customers’ services. Media and civil society organisations that someone is trying to silence. Energy and utility services, for which dispatchers’ communication during an incident is critical.

For all of them, it matters not only to repel the attack but also to keep people in touch while it lasts. That is why the protection is built into the same node through which messenger, mail and calls work.

What exactly is protected

The protection covers everything that runs through the CUBRA Node and CUBRA Shield modules: employees’ messages, calls, meetings and mail, CUBRA VPN connections and the link between offices, as well as your services published through the node. So under attack, people keep messaging and coordinating, even if the organisation’s other services have stopped (office-to-office channel — after release).

How we plan protection together with you

  • We list the services whose outage would cost the most.
  • We choose the node form: Edge, Rack, Virtual or a cluster with redundancy.
  • We plan backup lines and entry points in the networks of different providers.
  • We set up alerts for duty officers and the procedure to follow during an attack.

After the attack

When the attack ends, CUBRA Console holds the full picture: when it started, how long it lasted, which entry points were in use and how quickly your people moved to new ones. You need this information for a report to the regulator or management, and to update the plan: add a backup line, move an entry point to another network, change the order of alerts. These reports contain no message or call content – only service events.

What a DDoS attack is in general and how to prepare for one is covered in the article “What is a DDoS attack and how to prepare for it”.

Frequently asked questions about DDoS protection

How is this different from ordinary DDoS protection?

Usually, traffic is handed over to a third-party scrubbing service, which sees all your requests. In CUBRA, protection is built into your own node, and the apps switch to new entry points on their own.

Does this protect the company website?

The protection covers services that run through CUBRA Node and CUBRA Shield: people’s communication, VPN and services published through the node. We will discuss your website at a meeting – it depends on where it is hosted.

Do employees need to do anything during an attack?

No. CUBRA apps switch to new entry points on their own. People notice at most a short pause (switching entry points under attack — in development).

Does this protect against attacks on the provider’s line?

If an attack completely saturates the provider’s line, no node inside the network can change that. For such cases, we plan backup lines and entry points in the networks of different providers together with you.

Can the protection be tested before a real attack?

Yes. During deployment, we test switching to backup entry points and the alert procedure together with you, so that everyone knows what to do during a real attack.

Does the protection work for a small company?

Yes. Protection is built into the compact CUBRA Node Edge as well. For a small company, the key things are a backup line and communication between people that will not stop during an attack.

How do I know an attack has started?

The duty officer receives an alert on their phone, and attack events and node status are visible in CUBRA Console.

How much does DDoS protection cost?

Nothing extra: DDoS protection is a basic part of every CUBRA Node, and you do not need to buy a separate traffic scrubbing service. You pay only for the node itself.

Is separate hardware needed?

No, protection is already built into every form of CUBRA Node: Edge, Rack, Virtual and cluster.

Let’s check what happens under attack

Tell us about your services – we will show you a plan for protection and backup entry points.

Request a demo →
Learn more