Clear Cybersecurity for Business
Four Guides to Start With
- Guide · NIS2 & Compliance#NIS2#KSC#Compliance
Does the KSC Act (NIS2) apply to you? How to tell in 10 minutes
Poland's cybersecurity law is already in force, and the deadlines and the director's personal liability are more alarming than the requirements themselves. It's hard for a director to tell whether the company falls under the law and what to do next.
Reduce the risk of large fines and personal liability for management.
What you'll learn- Who the law covers: how your sector and company size determine your status
- Key dates and what needs to be done by April 3, 2027
- What the company and the director personally face for not meeting the requirements
Related service:Risk Reduction during AuditsComing soon - Guide · Infrastructure & Servers#backups#outages#infrastructure
Backups are “being made,” but no one has ever tested restoring from them. The problem comes to light on the day of an outage, when it's too late.
Make sure your clients' data is safe and reduce the risk of sudden downtime.
What you'll learn- Where to keep backups so you don't lose them along with the main system
- How to run a test restore and record the actual downtime
- What people usually forget to back up, and who should be responsible for checking
- Guide · AI Security#AI#AIsecurity#leaks
What not to send to AI chats: basic rules for employees
Employees use AI assistants to work faster, and along with their text they paste in client databases and source code. There are no rules yet, but the risk of a leak is already here.
Keep trade secrets and client data under control when working with AI.
What you'll learn- What data must not go into AI services: personal data, contracts, code, keys, and passwords
- How to allow convenient use of AI while keeping it safe
- How to explain the rules to your team and who is responsible for the outcome
Related service:AI SecurityComing soon - Guide · Data Protection (RODO)#RODO#GDPR#breach#incidents
Data leak or breach: what to do in the first 72 hours
After a leak or breach, a company has very little time. Under RODO, you may need to report the breach to UODO within 72 hours, and it's important not to lose that time to panic.
Stop the problem, protect your reputation, and reduce the risk of regulatory sanctions.
What you'll learn- First steps: stop the problem and preserve data for the investigation
- How to assess the risk to people and when to notify UODO and clients
- How to document decisions to limit the damage and the regulator's questions
Related service:Emergency Help Upon BreachComing soon
New in the Hub
- Guide · NIS2 & Compliance
NIS2 and the KSC Act in plain terms
A short explanation of what has changed for companies in Poland and where to start.
#NIS26 Nov 2026 · 5 minRelated service:Risk Reduction during Audits - Guide · AI Security
What prompt injection is and why it's dangerous for your bot
How outside text can make a bot or agent act differently than intended.
#AI#bots30 Oct 2026 · 6 minRelated service:AI Security - Checklist · Infrastructure & Servers
Two-factor authentication: where to turn it on first
A list of services where account protection does the most good.
#accounts23 Oct 2026 · 4 minRelated service:Technical Security Audit - Guide · Data Protection (RODO)
Data leak: what to do in the first 72 hours
The order of actions and the questions you need to settle right away.
#RODO#leaks16 Oct 2026 · 7 minRelated service:Emergency Help Upon Breach - Case Study · Incidents & News
Case study of a recent incident: how it happened and how to avoid it
What happened, where the weak point was, and which measures would have helped.
#incidents9 Oct 2026 · 6 minRelated service:Emergency Help Upon Breach - Guide · For Developers
Secrets in code: how not to lose keys in your repository
Where keys end up in code and how to set up automated checks.
#CI/CD#secrets2 Oct 2026 · 5 minRelated service:Security for Developers
Download and Use Right Away
- 10questions
10-Question Checklist: NIS2 / KSC Readiness
10 questions about processes, access, and documents to spot gaps early, not during an inspection. Go through an inspection with less stress and reduce the risk of fines for the company and its management.
Get the PDF by email - 7questions
7 Questions for IT Team: Director's Liability Cheat Sheet
The 7 key questions a director should ask their IT team today. Take control and reduce your personal financial risk.
Get the PDF by email - 1policy
AI Usage Policy Template for Employees
A ready-made policy you can adapt to your company and roll out right away. Help your team use AI effectively, with less risk of data leaks.
Get the PDF by email
What's Happening Right Now
Recent breaches, AI-driven attacks, fines, and new laws. Under each story, we explain how the situation could have been avoided.
- Breach
Medical data of nearly 19 million people stolen from the MyDr platform
Poland's digital affairs ministry reported a cyberattack on MyDr, whose services are used by around 12,000 medical facilities. More than 2 TB of data were stolen, including names, PESEL numbers, contact details, and consultation and prescription records. The prime minister said the attack appears to be an extortion attempt.
Sources: Notes from Poland, Polskie RadioHow it could have been avoidedLimited access to databases, monitoring of bulk data exports, and a rehearsed incident response planWhat We Do - AI
Prompt injection in Microsoft and Salesforce AI agents led to data leaks
Capsule Security found flaws in Microsoft Copilot Studio and Salesforce Agentforce that let attackers use public forms to make the agents exfiltrate sensitive corporate data. Both companies have released patches.
Sources: OECD.AIHow it could have been avoidedGive agents no more access than the task needs, treat any text from forms as untrusted, and require human approval before data leavesWhat We Do - Fine
UODO imposed 32 fines totaling nearly PLN 64.5M in 2025
That is more than four times the previous year, when fines came to about PLN 13.9M. According to the UODO president, the most serious failures concern data security, and fines also cover late breach notifications. The largest fine, over PLN 27M, went to Poczta Polska.
Sources: Infor.plHow it could have been avoidedThe technical side of GDPR: who can access data, how it is protected, and how to notify UODO within 72 hoursWhat We Do
Ask the Experts
Ask a question about your business's security and get an answer from an engineer. We'll publish the best questions and answers here.