Auto Secure Login logoAuto Secure LoginPlatform Discord
Menu

For penetration testers, RF researchers, MSPs, and anyone who has to prove a test stayed in scope

Tools for security teams and authorized testing

Security teams & authorized testers

You have the skills and the authorization letter. What you do not have is a way to prove, six months later, that the RF envelope you transmitted in was the one the client signed, that the scan was read-only, or that the device you blocked was blocked for a documented reason.

Most teams keep that record in a spreadsheet nobody can verify and a chat thread nobody can find. When a client, an auditor, or a regulator asks "show me", the answer is a shrug and a screenshot.

What changes for you. Signed scopes, receive-only field surveys, host defense that never locks you out, and an attacker's-eye assessment your customer authorizes and your analyst verifies. Every engagement leaves a record that proves itself.

The products on this path

In the order most people adopt them.

SI
Live

SignalLab

Security & RF intelligence

Signed, bounded authorization for lab-only RF and Wi-Fi testing, plus a monitor-mode bench kit for your own workstation.

Who it is for: Product security and RF test labs validating garage, gate, vehicle-keyless, and sub-GHz controller fixtures on a bench

Explore →
BA
Live

BandSight

Security & RF intelligence

See what is actually transmitting around you — a receive-only radio survey run from a phone and a low-cost USB receiver.

Who it is for: Security consultants and field assessors who get asked "is anything transmitting here that shouldn't be?" and need a defensible answer

Explore →
SC
Live

ASL Scan

Security & RF intelligence

Signed-scope security assessments your client authorizes, your analyst verifies, and no one can quietly edit after the fact.

Who it is for: Managed service providers who assess client systems and need proof, not promises

Explore →
LU
Available now

LurkerLock

Security & RF intelligence

Host security for Windows PCs and Linux servers. It watches each machine, sets decoys, blocks attackers when you allow it, and keeps the record on a server you run.

Who it is for: Small businesses with a few Windows PCs and Linux servers and no security team to watch them

Explore →
NS
Live

Network Sentinel

Security & RF intelligence

A running record of every device on your network, and an alert the moment something new joins.

Who it is for: A small-business owner who runs the office Wi-Fi and has no IT department

Explore →
X-
Available now

ASL X-Ray

Security & RF intelligence

Read what an Android app can do before you install it, without ever running it.

Who it is for: The one person at a small company who gets asked "is this app safe to put on the work phones?"

Explore →
TA
By arrangement

ASL Timestamp Anchor

Data protection & digital trust

Independent proof that your file existed at a moment in time, without uploading the file.

Who it is for: A therapist whose progress notes could be reviewed by a licensing board years after they were written

Explore →
VA
In-house tool

ASL Vault

Data protection & digital trust

A credential store you can add to while it is locked. Only your passphrase opens it.

Who it is for: The one person who ends up holding every key for a small company: API keys, app signing material, account recovery codes, backup passphrases

Explore →

Objections

The questions you are already asking.

We already use commercial scanners.

Keep them. ASL Scan is about the authorization and evidence around a test, not about replacing a vulnerability database. SignalLab and BandSight cover RF work no commercial scanner touches at all.

Does any of this transmit or exploit on its own?

No. SignalLab is a paperwork-and-proof layer with no transmit control. BandSight is receive-only. LurkerLock blocks only after you turn blocking on, starts as a dry run, and never blocks your own network or management addresses. Active adversary emulation in Scan runs only inside a signed plan with bounded traffic.

What happens to our data if we stop paying?

Your manifests, reports, and receipts are files you hold. They verify with standard tools after the service is gone. Nothing is held hostage.

How it starts

Start small, prove it, then grow.

Map

We agree on who will use it, what problem it solves, what a good result looks like, who decides, and what is out of scope.

Prove

We build the smallest version that is useful, and you test it against the result you defined.

Accept

You review what was built, what risk is left, and how you would leave, all in writing.

Expand

We add more only when it improves the result.

Define an authorized review.

One conversation. No specification needed. No customer data needed for the first call.

Help / Ayuda