When hackers come as a swarm of AIs

ParviDefenders watches, fights, builds what is missing, and leaves you a book nobody can rewrite.

Plain English. Male voice. The film takes its time. It ends on the book you can review.

The pain it solves

Your security people are human. They work in shifts. They look at screens. They go home. They look again in the morning.

The new attacker is not one person at a keyboard. It is a swarm of AI agents — many small programs working together. They try many doors at once. They share what they find with each other. They write new tricks while the attack is still on. They do not sleep. They do not wait for Monday.

So the pain is simple, even if it is ugly:

• You often find out after. The swarm already tried thousands of doors while people were asleep or in a meeting.
• Nobody built a new lock during the fight. The tools you already had only knew yesterday’s rules.
• Afterwards, the story is soft. Ordinary logs are files. Whoever holds the server can edit a file. The board, the regulator, or a court cannot be sure what the machines really did.

That is the hole. ParviDefenders is built to close it: see it now, act now with rules a person already set, build a missing tool if you must, and leave a sealed book of every agent act.

Why ParviDefenders

It is four jobs working together, at the speed of the swarm. Not four slogans. Four people-shaped roles, done by agents:

Watch (Aegis). Think of someone who never leaves the door. It sits on the login you see and on the machines behind it. When a storm of wrong passwords starts, or someone knocks on a fake door you planted to catch a thief, or a hidden way opens on the machine, the watch sees it while it is happening. Then it wakes the other three. You are not waiting until Monday.

Fight (Michael). The fighter is not free to do anything. He has a short list of tools a person already allowed — like a guard who may lock a door, and may not go punch people in the street. He looks first. He closes the hole he is allowed to close. He does not invent a new weapon in the dark. He does not attack the attacker back. That limit is the point. Speed without a leash is another attacker.

Build (Forge). Sometimes the allowed list is missing a tool. In this film, a lock after too many wrong passwords was missing. The builder uses extra hands — live terminals — to write that tool during the fight. It tests the program. The file is on disk. You can open it. A person still has to say yes before the fighter may use that new tool. The machines are fast. A person stays in charge of new weapons.

Record (Escudo, and the book). The reporter writes a pack a human can read, and send to police if a person decides to. Every act the agents took also goes into a cryptographic book: numbered, sealed, reviewable. That is not a story someone typed later. It is the fight, written as it happened.

If you face that swarm without this

The attack can be over in minutes. The argument about the logs lasts for years.

• You find out after. A swarm already tried thousands of doors. A person in a chair cannot match that speed.
• Nobody builds a defense in the fight. You only have the tools you installed last year. The swarm is writing new tricks today.
• Logs can be disputed. A file on a server is not a sealed book. Whoever holds the machine can change a line and say “that is what happened.”
• You have screenshots and opinions. You do not have a numbered record of what each agent did — for the board, the regulator, or the police. When they ask “what did the machines do?”, you shrug, or you guess.

The book the film ends on

This is what ParviDefenders do. And you get all of it written as a cryptographic record.

An agent acts. That step is numbered. It is sealed so it cannot be edited later. You open the book and read what happened. If someone tries to change a line after the fact, it will not match.

You can review it. No alteration can be done on those logs. That book is yours after the fight.

What you are watching in the film

This is a training copy of a company login. Fake users. A real Sign in, with email and password. Not a live shop. An attacking swarm hits this copy only, so we can show you the four jobs without touching a real customer.

The red windows are the swarm. The others are the four jobs. Nine live terminals. You are seeing what they typed, not a drawing of a battle.

1. The attacker tries the login as a storm — wrong password, again and again, then too many attempts.
2. It knocks on a fake door we planted, to see if a thief is probing.
3. It opens a hidden way on this machine.
4. The watch sees all three and wakes the others at the same moment.
5. The fighter looks, then closes that hidden way — with an allowed tool. The hole is gone.
6. The builder writes a lock program during the fight. The test passes. The file is on disk.
7. A person says yes. Then the login answers locked. After the exercise we unlock the training copy so it still works.
8. The reporter writes the pack. Police send stays a person.
9. Every act is in the sealed book.