Security for gaming companies: the anatomy of a launch-day DDoS and how Decripte structures the defense
Game servers going down at launch peak, hijacked player accounts, rare items drained, and a defrauded virtual economy. Decripte mitigates at the edge, monitors 24x7, and responds to incidents with containment in under one hour.
Direct answer
To protect a gaming company you need four layers working together: anti-DDoS mitigation at the edge capable of absorbing volumetric attacks of tens of Tbps before they reach the game servers; defense against account takeover (MFA, credential stuffing detection, and login bot monitoring); virtual economy anti-fraud (velocity rules, item laundering detection, and marketplace transaction review); and a SOC 24x7 with incident response that contains the event in minutes, not hours. Decripte delivers these layers in an integrated way: Edge Security with always-on WAF/anti-DDoS, SOC 24x7 monitoring login and game traffic, Pentest of the client and the server, continuous Vulnerability Management, and Incident Response with a containment SLA of one hour or less. Start with the free assessment at decripte.com.br/intelligence-center and sign up at decripte.io/start.
24/7
SOC monitoring login and game traffic
<=1h
Incident containment SLA
LGPD
Player data as personal data
PCI-DSS
Requirement for in-game payments
In summary
- ›The gaming sector is the most targeted by DDoS in the world, and attacks concentrate on launches, updates, and competitive events, when the entire user base is online and tolerance for downtime is minimal.
- ›Volumetric DDoS has already exceeded 29 Tbps in 2025 (the Aisuru botnet against Steam, Riot, and PSN). Without edge mitigation, no game data center absorbs that volume on its own.
- ›Account takeover through credential stuffing is exploding because players reuse passwords. Every third-party breach becomes ammunition against your login platform.
- ›The virtual economy (items, skins, in-game currency, NFTs) has real value and is a target for fraud, laundering, and the draining of compromised accounts.
- ›Player data is personal data under the LGPD; in-game payments fall within PCI-DSS scope. Incidents carry a duty to notify the ANPD and the data subjects.
- ›Decripte structures the defense at the edge, login, economy, and 24x7 monitoring, with incident response contained in under one hour.
Cibersegurança para Edtechs
Game servers going down at launch peak, hijacked player accounts, rare items drained, and a defrauded virtual economy. Decripte mitigates at the edge, monitors 24x7, and responds to incidents with containment in under one hour.
Why gaming platforms are a permanent target
A gaming company concentrates, in a single environment, almost everything an attacker wants: a huge base of users active simultaneously, an internal economy with real financial value, latency as a product requirement (any extra millisecond degrades the experience), and a maximum exposure window at the moments of greatest visibility — the launch of a title, the start of a competitive season, or the launch of a seasonal event. It is precisely during these peaks, when tolerance for unavailability is zero and the brand is in the spotlight, that the sector is attacked the most.
Recurring traffic research shows that the gaming sector is, year after year, the most targeted by distributed denial-of-service (DDoS) attacks in the world. The reason is both economic and psychological: taking down a game server at launch generates immediate reputational damage, refunds, negative reviews, and the loss of players who never return — which makes the company a perfect target for extortion. DDoS-for-hire groups and botnets offer the attack as a service for low prices, and players frustrated in competitive matches even hire attacks against opponents and against the platform itself.
The sector most attacked by DDoS
2025 mitigation reports place the gaming segment at the top of DDoS targets. In the fourth quarter of 2025, the Aisuru botnet was behind a record attack of approximately 29.69 Tbps hitting Steam, Riot Games, and PlayStation Network simultaneously. No game data center absorbs that volume in isolation: mitigation needs to happen at the edge, distributed globally, before the traffic reaches the origin infrastructure.
Add to this the credential vector. Because players reuse passwords across services, every breach of any random site becomes ammunition for credential stuffing against your login platform. Account takeover operations test billions of email and password combinations per month using botnets, and the goal is not just to steal the account — it is to drain the item wallet, transfer rare skins, abuse promotions, and resell the access. The attack surface of a gaming company, therefore, is not a server: it is the sum of the edge, the authentication flow, the virtual economy, and the game client.
The five threats that define the risk of a gaming company
1. DDoS against the game servers
It is the most visible threat and the one that most often takes down launches. There are three families: volumetric (floods the link with traffic — UDP flood, DNS/NTP amplification, IoT botnet attacks in the range of tens of Tbps); protocol (exhausts the state tables of firewalls and load balancers with SYN flood, fragmentation); and application layer (L7), the most dangerous for games, which mimics legitimate players by opening matchmaking, login, or game API connections to exhaust CPU and connection pools with little volume. L7 attacks are the ones that slip past poorly calibrated defenses because they look like real traffic.
2. Account takeover and item theft
Automated credential stuffing tests leaked credential lists against your login. When it hits, the attacker empties the account: transferring tradeable items, in-game currency, skins, and any asset with resale value. Without MFA and without bot detection at the login edge, the attack is silent and at scale — the player only finds out when the inventory is gone, and the support ticket becomes a reputation crisis.
3. Virtual economy fraud
The game's internal economy is a real financial system. Attackers exploit item duplication through bugs (item dupe), marketplace arbitrage, item laundering between accounts (laundering of skins obtained via stolen accounts or fraudulent cards), abuse of bonuses and promotions, and chargeback fraud with cloned cards that buy currency, spend it, and then reverse the charge. Each of these erodes the economy, inflates internal inflation, and harms legitimate players.
4. Cheating and client exploitation
The game client runs on the player's machine, outside your control. Cheats (aimbots, wallhacks, speed hacks) exploit the client's memory, packets, and APIs. More serious from a security standpoint: the same reverse-engineering techniques that produce cheats uncover vulnerabilities in the client-server protocol that allow command injection, state forgery, and, in extreme cases, remote execution on the server from malformed packets.
5. Player data breach
Game databases store email, name, date of birth (parental controls and age), purchase history, payment data, and often chat conversations. It is a valuable and regulated target: under the LGPD these are personal data, and some of them (the age of minors, for example) may receive enhanced protection. A breach triggers the duty to notify the ANPD and the data subjects, on top of the brand damage.
The L7 attack is what takes down launches
Volumetric DDoS is detected and mitigated by edge capacity. The application-layer attack, which mimics real matchmaking and login, is the one that goes unnoticed: a few gigabits of traffic take down the backend because each request costs CPU and a long-lived connection. Defending games requires behavioral fingerprinting (not just volume) and rate limiting per game endpoint, not just per IP.
Is edtechs data already exposed or up for sale? Find out now — for free.
Sem cartão, sem compromisso. Descubra em minutos o que já vazou da sua empresa e qual é o seu risco real.
Technical anatomy of a launch-day DDoS
It is worth understanding the mechanism, because the correct defense depends on it. A launch is announced with a date and time. Attackers know exactly when the entire base will be connected and when maximum damage is possible. The attack usually combines vectors in waves.
Wave 1 — link saturation (volumetric)
A botnet of compromised IoT devices (routers, cameras, DVRs) fires amplification traffic. In 2025, attacks of this type exceeded 29 Tbps. The goal is to clog the data center's uplink before any application rule matters. If the company relies solely on the capacity of its own data center, the link saturates and everything goes down — including unrelated services that share the same network.
Wave 2 — state exhaustion (protocol)
SYN floods and fragmentation exhaust the connection tables of firewalls, load balancers, and the kernel of the game servers themselves. Even if the link holds, the network devices stop accepting new connections — legitimate players cannot even begin the handshake.
Wave 3 — application flooding (L7)
The most surgical wave. Bots mimic real clients and hammer the most expensive endpoints: authentication, matchmaking, session creation, inventory queries. Each request seems legitimate individually, but the aggregate volume consumes CPU, database pools, and long-lived connections. This is where defenses based on volume alone fail.
Why mitigation has to be at the edge
The only effective defense against Wave 1 is to absorb and filter the traffic in a globally distributed mitigation network, with multi-Tbps capacity, before it reaches the origin. Decripte structures Edge Security so that game traffic passes through scrubbing: the volumetric is dropped at the edge, the protocol is normalized, and the L7 is filtered by reputation, behavioral fingerprint, and rate limiting per game endpoint — preserving the real player and blocking the bot.
How Decripte mitigates at the edge and protects the virtual economy
The defense of a gaming company is not an isolated product, it is a system. Decripte combines always-on edge mitigation, continuous monitoring of the authentication flow, anti-fraud rules in the economy, and a SOC 24x7 that correlates signals across these layers. A spike in failed logins combined with an increase in rare item transfers, for example, is not a coincidence — it is the signature of an ATO in progress, and the SOC treats both events as a single incident.
Edge: scrubbing and WAF for games
Traffic enters through a distributed mitigation layer. Volumetric and protocol attacks are absorbed and dropped before the origin. A WAF tuned for games protects the game APIs and the login and marketplace endpoints, with rate limiting rules specific to each endpoint, challenges for suspicious traffic, and blocking of known botnet signatures. The origin is never directly exposed.
Login: barrier against credential stuffing
MFA available and encouraged, bot detection at the login edge, analysis of the velocity and geography of attempts, blocking of known leaked credentials, and progressive challenge. The goal is to make automated credential testing unfeasible without adding friction for the legitimate player.
Economy: item and transaction anti-fraud
Velocity rules on item transfers, detection of laundering patterns (new accounts that receive rare items and pass them along), review of high-value marketplace transactions, chargeback signals, and quarantine of suspicious assets. The idea is to treat the virtual economy with the same rigor as a financial anti-fraud system.
What Decripte sets up for a gaming company
- ✓Always-on anti-DDoS mitigation at the edge (volumetric, protocol, and L7)
- ✓WAF tuned for game APIs, login, and marketplace
- ✓Login protection: MFA, bot detection, and blocking of leaked credentials
- ✓Virtual economy anti-fraud: velocity rules, anti-laundering, and transaction review
- ✓SOC 24x7 correlating login, game traffic, and economy
- ✓Pentest of the game server, the client, and the client-server protocol
- ✓Continuous Vulnerability Management on the infrastructure and dependencies
- ✓Incident response plan with containment in under 1 hour
Game-specific pentest and vulnerability management
Testing the security of a gaming company goes beyond a traditional web pentest. There are three distinct surfaces, and each one requires its own technique.
The client-server protocol
The heart of an online game is client-server communication. Decripte tests whether the server trusts data from the client (the root flaw behind most cheats and exploits), whether it validates and authorizes each command, whether injection is possible via malformed packets, whether the game state is authoritative on the server, and whether there are exploitable race conditions in item and currency transactions.
The game client
The binary runs on the player's machine. The pentest evaluates reverse engineering, memory manipulation, client integrity, protection of embedded secrets (API keys should never be in the client), and the robustness of the anti-tamper. The goal is to raise the cost of exploitation and ensure that the server does not blindly trust the client.
The infrastructure and the APIs
Matchmaking servers, game APIs, admin panels, payment backends, and the cloud infrastructure. Here the OWASP repertoire applies (including the API flaws), authentication and authorization testing, environment segregation, and surface exposure. Vulnerability Management turns the pentest into a continuous process: new dependencies, new builds, and new endpoints enter recurring scanning, with prioritization by real business risk.
OWASP as a reference, not as a magic number
Decripte uses the OWASP references (Top 10 web and API Security Top 10) as the methodological basis of the pentest, without reducing the work to a checklist. In games, the most critical flaws tend to be business logic ones — broken authorization in item transactions, undue trust in the client, race conditions in the economy — that no automatic scanner finds.
What would an incident in edtechs cost? See your real risk before it happens.
Sem cartão, sem compromisso. Descubra em minutos o que já vazou da sua empresa e qual é o seu risco real.
Compliance: LGPD, PCI-DSS, and player data
Gaming companies operate under concrete regulatory obligations, and ignoring them turns a technical incident into a legal crisis.
LGPD and ANPD
Player data is personal data. Email, name, date of birth, purchase history, and chat fall under the General Data Protection Law. The company needs a legal basis for the processing, technical and administrative security measures, and a response plan that includes, in the event of an incident with risk to the data subjects' rights, notification to the National Data Protection Authority (ANPD) and communication to the affected data subjects. The processing of data of children and adolescents receives special attention under the LGPD — relevant to any game with a young audience.
PCI-DSS
The moment the platform processes, stores, or transmits card data for the sale of currency, passes, or items, it falls within PCI-DSS scope, the security standard of the card industry. Even when processing is outsourced to a gateway, the way the integration is done determines the scope and the responsibility. Decripte helps design the architecture to reduce scope and meet the applicable controls.
Notification is not optional
Under the LGPD, a breach of player data that may pose a relevant risk to the data subjects requires communication to the ANPD and to those affected within a reasonable timeframe. Having an incident response plan that already covers this step — with impact assessment and an evidence trail — is what separates a controlled notification from a public crisis. Decripte structures this flow before the incident happens.
The SOC 24x7 and correlation across layers
The operational differentiator in games is correlation. Isolated events deceive; patterns give it away. An increase in failed logins may be credential testing. A spike in rare item transfers may be account draining. A slight increase in latency on specific endpoints may be the start of an L7. Looked at separately, each may pass as noise. Correlated in real time by a SOC 24x7, they reveal the attack while it is still containable.
Decripte monitors edge traffic, the authentication flow, game telemetry, and virtual economy events without interruption, with playbooks ready for each scenario in the sector. When a signal crosses the threshold, the team does not start thinking about what to do — it executes an already validated runbook, with the edge ready to scale mitigation and the on-call engineering team informed.
What the SOC watches on a gaming platform
- ✓Edge traffic: volume, geography, reputation, and botnet signatures
- ✓Login: failure rate, velocity, devices, and leaked credentials
- ✓Economy: item transfers, marketplace transactions, and laundering signals
- ✓Game telemetry: latency per endpoint, long-lived connections, matchmaking anomalies
- ✓Payments: chargeback patterns and buy-and-reverse
- ✓Integrity: client tamper alerts and protocol exploitation
Launch under fire: an anonymized anatomy of a day-zero DDoS
Real, de-identified example
A real anonymized example (without identifying the client). A mid-sized Brazilian studio prepares the global launch of a competitive multiplayer title. Date and time announced, expected simultaneous peak in the hundreds of thousands of players, an internal economy with a marketplace of tradeable skins and the sale of a season pass by card. The infrastructure runs in the cloud, with matchmaking servers and game APIs exposed. Before the launch, Decripte takes over Edge Security, the SOC 24x7, and keeps an Incident Response plan on standby for the critical window.
Pre-launch (D-7)
Decripte performs a pentest of the client-server protocol, the game APIs, and the payment flow, and closes an authorization flaw that allowed querying the inventory of other accounts. Edge mitigation is set to always-on, with the WAF tuned for the login, matchmaking, and marketplace endpoints, and the DDoS and account takeover runbooks validated with the studio's team. Multi-Tbps scrubbing capacity confirmed.
Detection (hour zero + 6 min)
At the minute of launch, the SOC detects Wave 1: a volumetric amplification spike coming from an IoT botnet, in the range of several Tbps, aimed at the uplink. Simultaneously, the SYN flood rate rises against the load balancers. The edge is already absorbing the volumetric; the protocol alert triggers the runbook.
Containment (in under 1 hour, peak at ~12 min)
Edge mitigation drops the volumetric traffic before the origin and normalizes the protocol traffic. Then Wave 3, the L7, begins: bots mimicking matchmaking and login flood the most expensive endpoints. The SOC activates progressive challenge, rate limiting per game endpoint, and blocking by behavioral fingerprint. The game server stays up; real players keep connecting. Containment within the one-hour SLA.
Parallel investigation
During mitigation, the SOC notices a second pattern: an increase in failed logins from distributed sources — credential stuffing trying to take advantage of the launch chaos. The correlation across layers treats DDoS and ATO as a single coordinated incident.
Eradication
The DDoS bot signatures are blocked at the edge. At login, known leaked credentials are blocked, MFA is enforced on high-value accounts, and the few compromised accounts have their sessions revoked and their transferred items placed in marketplace quarantine for reversal.
Recovery
The service stabilizes with legitimate players online throughout the event. No rare item leaves the ecosystem irreversibly; the suspicious transactions in quarantine are reversed after analysis. The launch concludes with no downtime perceptible to the public.
Lessons and structuring
The post-incident review recommends default MFA for accounts with tradeable items above a value threshold, permanent velocity rules in the marketplace, continuous monitoring of leaked credentials, and a tabletop exercise before each new launch or season. Everything enters Vulnerability Management as a recurring process.
Outcome with Decripte
The launch took place with no visible downtime, the virtual economy remained intact, and no player data was exposed. What could have been a catastrophic day zero — servers down, negative reviews, refunds, and extortion — became an operational event contained by Decripte within the SLA. The difference was not a single product, but the combination of edge, SOC 24x7, anti-fraud, and a response plan rehearsed before the critical hour.
Don’t wait for the incident. Start hardening edtechs today.
Comece pelo diagnóstico gratuito agora e veja em minutos o que já vazou. SOC 24x7 e contenção em até 1h nos planos pagos.
How Decripte responds to an incident at a gaming company
When the server goes down at launch or accounts start being drained, every minute costs players, revenue, and reputation. Decripte's response follows a rehearsed flow, with containment in under one hour.
- Detection and triage: the SOC 24x7 correlates signals from the edge, login, economy, and game telemetry, classifies the incident (volumetric DDoS, L7, ATO, economy fraud, or breach), and triggers the corresponding runbook without wasting time deciding what to do.
- Immediate containment at the edge: for DDoS, distributed mitigation drops the volumetric before the origin, normalizes the protocol, and applies challenge, rate limiting per endpoint, and blocking by fingerprint against the L7. For ATO, suspicious sessions are revoked and MFA is enforced. Containment target: one hour or less.
- Investigation and correlation: the team identifies whether more than one vector is acting together (DDoS used as a smokescreen for credential stuffing, for example), preserves evidence, and maps the reach — which accounts, which items, which data.
- Eradication: attack signatures blocked, leaked credentials barred, compromised accounts isolated, fraudulently transferred items placed in marketplace quarantine, and the root flaw (protocol bug, endpoint without rate limit, broken authorization) fixed.
- Recovery: service restoration with validation that legitimate players have returned, reversal of fraudulent transactions in quarantine, and confirmation of virtual economy integrity.
- Regulatory notification when applicable: if there was access to personal data with relevant risk, Decripte supports the communication to the ANPD and to the data subjects within the LGPD timeframe, with impact assessment and an evidence trail.
- Post-incident and hardening: report with a timeline, root cause, and recommendations; permanent adjustments to the edge, login, and economy enter Vulnerability Management as a continuous process.
- Readiness exercise: a tabletop before the next launch or season, validating runbooks with the studio's team so that the next critical window is even better protected.
How Decripte structures the security of a gaming company
Responding well to an incident matters, but the goal is for it not to take down the service. Decripte structures the defense in pillars that operate in an integrated and continuous way.
Always-on anti-DDoS mitigation at the edge
A distributed scrubbing network with multi-Tbps capacity to absorb volumetric and protocol traffic before the origin, and a WAF tuned for games to block the L7 that mimics matchmaking and login. The origin is never directly exposed, and mitigation scales automatically during launch peaks.
Login defense against account takeover
MFA encouraged, bot detection at the login edge, blocking of leaked credentials, analysis of velocity and geography, and progressive challenge. It makes credential stuffing economically unfeasible without adding friction for the legitimate player.
Virtual economy anti-fraud
Treating the internal economy as a financial system: velocity rules on transfers, item laundering detection, review of high-value marketplace transactions, chargeback signals, and quarantine of suspicious assets for reversal.
Continuous Pentest and Vulnerability Management
Testing of the three surfaces (client-server protocol, game client, and infrastructure/APIs) with an OWASP methodological basis, turned into a recurring process that follows new builds, dependencies, and endpoints with prioritization by real risk.
SOC 24x7 with cross-layer correlation
Uninterrupted monitoring that cross-references the edge, login, economy, and game telemetry to detect the attack while it is still containable, with sector-specific playbooks and on-call engineering during the critical windows.
Regulatory and response readiness
Incident Response plan with a containment SLA of one hour or less, runbooks rehearsed before launches, and a notification flow to the ANPD and the data subjects already designed for the case of a player data breach.
Recommended plans for Edtechs
Edge Security
It is the layer that keeps the game server up at launch. Distributed anti-DDoS mitigation (volumetric, protocol, and L7) plus a WAF tuned for login, matchmaking, and marketplace, absorbing attacks of tens of Tbps before the origin.
See plan →SOC 24x7
Games are attacked precisely at the peaks, outside business hours, during launches and events. The SOC 24x7 monitors and correlates the edge, login, and economy in real time to detect DDoS and account takeover while they can still be contained.
See plan →Pentest
The most serious risk in games is business logic: undue trust in the client, broken authorization in item transactions, and flaws in the client-server protocol. Decripte's Pentest covers client, server, protocol, and APIs, finding what no scanner finds.
See plan →Vulnerability Management
Every new build, dependency, and endpoint expands the surface. Continuous Vulnerability Management follows the studio's release cycle and prioritizes fixes by real risk to the business and to the virtual economy.
See plan →Frequently asked questions
How do I protect my game server from going down on launch day due to DDoS?
The effective defense is always-on edge mitigation, not reactive mitigation. Traffic needs to pass through a distributed scrubbing network with multi-Tbps capacity that drops the volumetric before the origin, normalizes the protocol, and filters the L7 (which mimics matchmaking and login) by rate limiting and behavioral fingerprint. Decripte sets this up before the launch and monitors it with a SOC 24x7. Start with the free assessment at decripte.com.br/intelligence-center.
What is account takeover and why are games such a target?
Account takeover is the hijacking of accounts, usually through credential stuffing: bots test credentials leaked from other services against your login, because players reuse passwords. Games are a target because the account holds assets with real value — items, skins, currency — that the attacker drains and resells. The defense combines MFA, bot detection at login, and blocking of leaked credentials.
How do I prevent virtual economy fraud and item laundering?
By treating the internal economy as a financial anti-fraud system: velocity rules on transfers, detection of accounts that receive rare items and pass them along (laundering pattern), review of high-value marketplace transactions, chargeback monitoring, and quarantine of suspicious assets for reversal. Decripte structures these rules integrated with the SOC.
Is player data regulated by the LGPD?
Yes. Email, name, date of birth, purchase history, and chat are personal data under the LGPD. There is a duty to have a legal basis and security measures, and, in the event of a breach with relevant risk to the data subjects, a duty to notify the ANPD and those affected. Data of children and adolescents receives special attention — relevant to games with a young audience.
Do I need to worry about PCI-DSS if I sell currency or a pass in the game?
Yes, the moment the platform processes, stores, or transmits card data, it falls within PCI-DSS scope. Even using a third-party gateway, the form of the integration defines your scope and responsibility. Decripte helps design the architecture to reduce scope and meet the applicable controls.
Is game pentesting different from website pentesting?
Quite. Beyond the APIs and the infrastructure (where the OWASP repertoire applies), game pentesting tests the client-server protocol (whether the server trusts data from the client — the root of cheats and exploits) and the game client itself (reverse engineering, memory manipulation, embedded secrets). The most critical flaws tend to be business logic ones in the economy, which no scanner finds.
How quickly does Decripte contain an incident?
Decripte's containment SLA is one hour or less. The SOC 24x7 correlates signals from the edge, login, and economy, classifies the incident, and executes an already validated runbook — instead of starting to improvise in the middle of the crisis. For a launch, the runbooks are on standby during the critical window.
Where do I start if I don't yet have any structured protection?
Start with the free Threat Management assessment at decripte.com.br/intelligence-center, which shows your real exposure. From there, Decripte recommends the set of plans (typically Edge Security, SOC 24x7, Pentest, and Vulnerability Management) suited to your size and your launch cycle. To sign up, decripte.io/start; to talk to the team, /contato.
Sector terms
- L7 DDoS (application layer)
- A denial-of-service attack that, instead of flooding the link with volume, mimics legitimate requests (login, matchmaking, inventory queries) to exhaust the server's CPU and connections with little traffic. It is the most dangerous for games because it looks like real players and slips past defenses based on volume alone.
- Credential stuffing
- An account takeover technique in which bots test, against your login, lists of credentials leaked from other services, exploiting the fact that many users reuse passwords. It is the main vector for account hijacking in games.
- Edge scrubbing
- A process in which incoming traffic passes through a distributed mitigation network that filters (cleans) DDoS attacks — dropping the volumetric, normalizing the protocol, and blocking the L7 — before it reaches the game's origin infrastructure.
- Item laundering
- A virtual economy fraud in which assets obtained illicitly (stolen accounts, fraudulent cards) are transferred between accounts to mask their origin and resell them as legitimate, corrupting the game's internal economy.
- ANPD
- The National Data Protection Authority, the body responsible for enforcing the LGPD in Brazil. In the event of a security incident involving personal data and relevant risk to the data subjects, the company must notify the ANPD and those affected.
- PCI-DSS
- Payment Card Industry Data Security Standard, the security standard of the card industry. It applies to any platform that processes, stores, or transmits card data — such as the sale of virtual currency, passes, or in-game items.
Decripte protects and responds to incidents in edtechs.
Pentest, 24x7 SOC, incident response with a 1-hour containment SLA and compliance — without building an internal team. Or start free by seeing what has already leaked from your company.