ZipLoom
Home
PricingSign InGet Your Live URL

security

Private Pages Check & Decoy Rows

Know When A Private Page Is Open, And When Someone Is Inside.

Updated

At a glance

Check up to 10 private paths daily while signed out, and plant a decoy row in your own database that alerts you when its link is opened.

  • Your Private Pages, Checked Daily
  • Open Means A Finding And An Alert
  • A Tripwire Inside Your Database
Sample. List your private paths and ZipLoom checks each one daily while signed out. A decoy row you plant in your own database tells you if someone is inside.

Why it matters

An admin page left open is found by whoever looks first, and an attacker reading your database leaves no trace you can see from outside. These are two different blind spots, and this feature covers one of each.

List up to 10 paths that should need a sign-in. ZipLoom requests each one every day while signed out and reports whether it was refused, redirected or open. An open page becomes a high-severity finding and an alert. A decoy is a fake credentials row you add to your own database with SQL ZipLoom gives you. It holds a link no legitimate user has a reason to open, so if the alert fires, someone was reading rows they should not have and acted on what they found.

A Locked Door And A TripwireIllustration · sample data
signed out/admin/billingrefusedopen → alertyour database+ 1 decoy rowlink usedSomeone read your rowsalert

What you get

Your Private Pages, Checked Daily

List up to 10 paths that should need a sign-in, such as /admin. ZipLoom requests each one every day while signed out and tells you whether it was refused, redirected or open.

Open Means A Finding And An Alert

A private page that answers without a sign-in becomes a high-severity finding and is sent to your alert destinations, so it does not wait for your next scan.

A Tripwire Inside Your Database

Create a decoy and ZipLoom gives you a fake credentials row to run in your own database. It holds a link no legitimate user has a reason to open.

Alerted The Moment It Is Used

If anyone opens that link, ZipLoom alerts you. A decoy that fires means someone was reading rows they should not have, and acted on what they found.

How It Works

  1. 1

    On a project's Protection tab, an Owner or Admin lists the private paths and saves them.

  2. 2

    Each path is checked daily while signed out and shows its result on the card.

  3. 3

    For a decoy, give it a label, copy the SQL shown once, and run it in your own database.

  4. 4

    Subscribe an alert destination to the two tripwire events in Settings → Alerts.

What this check inspects

  • Whether each listed path answers a signed-out request, is refused, or redirects to sign-in.

  • Whether anyone opens the link stored in a decoy row.

What it means when this fails

An admin page left open is found by whoever looks first. The daily check makes sure that is you. A path that cannot be checked says so; it is never counted as protected.

What it does not do

  • A decoy cannot detect a plain read of the row. The alert fires only when the link inside it is used.

  • ZipLoom never connects to your database for decoys. You run the SQL yourself.

  • Paths that change something, such as sign-out or delete, are refused, so the check can never act on your app.

Questions

Does ZipLoom connect to my database for decoys?
No. ZipLoom gives you the SQL and you run it yourself. ZipLoom only sees when the decoy's link is opened.
Will it detect someone just reading the decoy row?
No. A plain read cannot be detected from outside your database. The alert fires when the link in the row is used.
Can it check pages that sign people out or delete things?
Paths that change something, such as sign-out or delete, are refused so that the check can never act on your app.

Related features