Security

Security for vibe-coding — 10 cards, translated to English. Читать по-русски →

All security cards — 10 in total

One password everywhere means one leak breaks everything. Two-factor auth plus a password manager shuts down 99% of account threats.

Everyone loses data eventually — the only question is when. The 3-2-1 rule and a tested restore turn a catastrophe into an inconvenience.

Collecting data and running paid ads are regulated by law. The liability sits with you as the data operator and the advertiser.

Someone else's skill or MCP server is someone else's code with your permissions. Skill marketplaces reviewed, plus safe-install rules.

Card details typed into someone else's form are a leaked card. Pay only through trusted services and over HTTPS, and use limited cards.

Whatever goes into someone else's AI can stay in their logs and training data. Filter what you paste and anonymise it first.

Content from the web, files or email can issue orders to your AI agent. Never let it act on them blindly — confirm risky steps.

"Double your crypto", investment bots, free API keys — all bait. An upfront payment or a seed phrase request means stop.

A leaked key means a breach and a bill for someone else's traffic. Keep secrets out of your code and out of your repository.

Bots scan an exposed server non-stop. Basic hygiene — SSH keys, a firewall, fail2ban — shuts the mass attacks down in five minutes.

Every card is vetted before it lands here: what the tool is for, how to set it up, and where it falls short. Browse all sections → · Read the in-depth guides →