Free security tools.
Clearer choices.

Organization administration and many team features require paid plans. Choose a team plan deliberately rather than sharing one personal vault.

You manage the database backup, master password, and any synchronization. Losing these can mean losing access.

The desktop app links to Signal on your phone. Plan how your organization handles devices, disappearing messages, and work records.

Mobile apps offer free read-only access; writing requires a paid unlock. Team administration is a separate product. Keep your recovery information safe.

This card covers uBlock Origin, not similarly named extensions or uBlock Origin Lite. Browser support differs; follow the project’s installation guidance.

Command-line setup and scheduled jobs need an owner. Storage may cost money; test a restore and protect the repository password.

Needs command-line administration. Protect the encryption key and passphrase, and verify that a restore works before relying on the archive.

A VPN needs key management, routing, and access rules. It protects the connection; it does not automatically make either endpoint trustworthy.

Back up important data and recovery information before changing storage encryption. Check current platform support and the project’s security guidance.

Signing in identifies you to that service. Downloads, browser changes, and device compromise can still expose information. Use the official platform guidance.

Use non-sensitive examples while learning. For confidential material, use an approved local copy and follow your organization’s handling rules.

Capture only authorized traffic. Packet files may contain sensitive information; control who can access them and where they are stored.

Agree on scope and timing before scanning. Review the Nmap license for redistribution, embedding, or commercial product use.

Use the project or your operating system’s trusted package channel. Limit the capture scope and handle saved traffic as sensitive data.

Requires traffic visibility, storage planning, and someone to interpret the records. It complements packet analysis rather than replacing it.

The professional edition adds features. Primarily designed for Windows; review the project’s guidance for other environments.

Traffic placement, current rules, and alert review matter. Start with a planned deployment and test changes before enabling blocking.

This is a dedicated system, not a desktop add-on. Check hardware requirements and prepare recovery before replacing a live gateway.

Needs a supported host and DNS configuration. Filtering can affect legitimate services; keep an owner and a way to troubleshoot exceptions.

DNSSEC validation and domain filtering solve different problems. Plan access restrictions and resolver settings before serving a network.

Requires suitable compute, storage, and administration. Review hardware requirements; paid support and commercial options are separate.

Central components require Linux; agents support Linux, Windows, and macOS. The platform needs maintenance. Hosted cloud offerings and support may be paid.

Needs supported runtime components and tuned rules. Alerts still need investigation; this is not a source-code vulnerability scanner.

Listed here as ZAP. Active tests can change data or disrupt a service; use an approved scope and suitable test environment.

The automated scanner and other professional features are not included. This is a manual testing toolkit that requires web security knowledge.

Command-line tool for authorized testing. Results need interpretation; correcting findings requires access to the service configuration.

Keep the scanner and databases current. Confirm findings against your deployed context; check installation support, including WSL where relevant.

Container deployment requires Linux and container administration. Feed updates, resources, and scan scope need ongoing management.

Requires technical judgment. A process name or a single indicator is not enough to establish whether something is malicious.

Review entries before changing them. Disabling the wrong item can break applications or device functionality.

Needs a suitable configuration and log collection plan. Check current Windows support; Sysmon records events rather than automatically resolving alerts.

Choose the utility that matches the task. Some tools can change system behavior and require administrative permissions.

Server and client deployment, access control, and collection scope need planning. Collected material can contain sensitive organizational data.

Needs query design and, for a fleet, management infrastructure. Results describe observed state and require context.

Keep signatures updated. A clean scan is not a guarantee, and the engine is not a complete endpoint protection program.

The report proposes improvements; it does not automatically fix the host. Evaluate recommendations before making production changes.

Key verification, revocation, backups, and compatible applications need planning. A signature is useful only when the signing key is trusted.