Skip to content

Keep it fixed, month after month.

New flaws are published every week, and systems drift. We keep watching your public exposure, rescan at least monthly, flag anything new at the scan that finds it, confirm your fixes held, and send a monthly report your leadership can actually read.

NEW EXPOSUREAlert sentOPEN FINDINGSMONTH 1MONTH 6RESCAN
Monthly reportSample
  • New this month1
  • Fixed and verified4
  • Still open6
  • Patches confirmed12
Illustrative figures.
Scans
At least monthly, on a schedule agreed with you.
Alerts
Sent when a scan finds something new.
Report
Monthly: new, fixed and still open.

What's included

Regular checks, not a one-time snapshot.

An assessment tells you where you stand on one day. This keeps telling you, so a new exposure is caught at the next scan, not at next year's audit.

  1. Everything internet-facing

    Your domains, websites, open services and remote access, scanned from the outside on a recurring schedule.

  2. Email spoofing watch

    SPF, DKIM, DMARC and certificates checked at every scan, so a quiet change never reopens the door to mail forged in your name.

  3. A named contact

    Questions about a finding go to an engineer who knows your environment.

Who it's for

For organizations that have done the first fix and want it to stay done.

Most teams start with an assessment or penetration test, close the findings, then move to monitoring so new problems are caught early.

  • You have closed your first round of findings and want to keep them closed.
  • Your board or insurer wants regular evidence, not a once-a-year snapshot.
  • Your IT vendor patches systems and you want independent confirmation.
  • You run many internet-facing systems and they change often.

How it works

A baseline, then a steady watch.

  1. Baseline

    Start from an assessment, or a first full scan, so every later change is measured against it.

  2. Schedule

    Agree scope, scan windows and who gets alerts.

  3. Scan and flag

    Scans at least monthly; anything new is flagged to you at the scan that finds it.

  4. Report

    A monthly report on what is new, fixed and still open.

  5. Verify

    Fixes and patches confirmed by rescan, and recorded.

Scan frequency and windows are agreed with you in writing. Reporting is monthly.

What you get

One report a month your board can read.

Monthly vulnerability report
  • New, fixed and still-open findings
  • Trend over time
  • Patches confirmed this month
  • What to fix next, ranked
Verification letter
After we retest your fixes, a signed letter stating what was fixed and how it was tested. Written to be handed to your board, insurer or auditor.
Monthly report · month 6Sample

Open findings by month

  • NewCertificate on portal expires in 14 days
  • FixedVPN appliance patched, confirmed by rescan
  • FixedMulti-factor enforced for all admins
  • OpenOld file server still reachable
Illustrative. Open findings fall as fixes are verified.
Ends with the signed verification letter

Questions

About the standing watch.

Something else? team@americasecure.com

At least monthly, on a schedule we agree with you based on how much you run and how often it changes. Reporting is monthly, and when a scan finds something new we flag it to you then, without waiting for the report. Monitoring is scheduled scanning, not a 24-hour watch desk.

No. Scanning finds known weaknesses broadly and often; a penetration test goes deep on a defined scope. They work best together.

No. Monitoring watches what anyone can reach from the internet, so nothing runs on your network.

The contacts you choose, such as your IT lead and your IT vendor. Each alert says what changed, why it matters and what to do.

Start with an evaluation.

Tell us about your organization. We start within 24 hours of your go-ahead, and nothing is tested without your written authorization.