Compliance

This is the Compliance demo. Every visitor shares this company, and it resets every night.

What you change here, everyone sees until the next reset. Email, payments, and the AI models are switched off.

Start your own trial
  • EU GDPR (2016)
  • ISO 27001:2022
  • NIS2
  • NIS2 Netherlands (Cbw, 2026)

Nothing found that matches the search criteria.

Start your own trial
SV
Sam de Vries
sam.devries@tidewell-it.example

Repeated failed logins on the remote desktop gateway

INC-007 - Last updated Open Medium
Edit

Description

Summary

The monitoring platform reported a steady stream of failed logins on the remote desktop gateway, hundreds per hour, from a single range of addresses abroad. The attempts used common user names one after another.

Impact

No account was compromised. Every attempt failed, and the gateway required a second factor on top of the password. The gateway did slow down during the busiest hour, and two customers noticed a delay when signing in.

Response

The engineer on call blocked the source range on the firewall and set the gateway to lock an account after five failed attempts. Extra alerting is in place, so a new range or a successful login after many failures reaches the on-call engineer directly. The logs are kept for a review of the gateway's exposure to the internet, which is still pending. The Incident stays open until that review has decided whether the gateway can sit behind a VPN.

Notifications

No customer data was involved, so no notification was needed. The affected customers were told about the slow sign-in and what we changed.

Title
Filename
Uploaded

No files attached yet.

Are you sure?

This action cannot be reverted.

Leave this page?

Your changes on this form are not saved. If you leave, they are lost.