Skip to content

Two ways to fix it. One standard of proof.

Every finding gets a fix and a retest. Our engineers make the change, or your own IT staff and vendors do, following a step-by-step plan from us. Then we sign a letter stating what was fixed and how it was tested.

FINDINGSRanked by riskDONE-FOR-YOUOur engineers fix itGUIDEDYour team fixes itSIGNED LETTERAfter a retest

Two paths

Pick a path for each finding.

Most organizations mix the two: we take the hard or urgent fixes, and their team handles the rest with our plan.

Done-for-you

Best when you have a small IT team, or a deadline.

  • A change plan you approve before anything changes
  • Work through named accounts you create and can switch off
  • Changes made in maintenance windows you choose
  • A record of every change: what, where, when

Guided

Best when you have IT staff or a vendor who can do the work.

  • A step-by-step fix plan for each finding, written for your systems
  • Vendor-ready instructions you can forward as they are
  • Our engineers on hand for questions while your team works
  • Findings ordered so the urgent ones get done first

Who it's for

For organizations that have findings and need them closed.

Usually that list comes from our assessment or penetration test. If you have a recent report from someone else, talk to us about working from it.

  • You have a findings list and not enough hands to work through it.
  • An insurance renewal, audit or grant deadline needs proof that issues are closed.
  • Your IT vendor will do the work but needs exact, system-specific instructions.
  • You want your own staff to learn the fixes, with an expert on call.

How it works

Plan, fix, retest, sign.

  1. Agree on the plan

    We go through the findings together and choose a path for each one: done-for-you or guided.

  2. Fix

    Our engineers make approved changes, or your team works from our step-by-step plan.

  3. Retest

    We test every fix. If one does not pass, we explain why and update the plan.

  4. Verify in writing

    A signed letter stating what was fixed and how it was tested.

We schedule changes in windows you approve, and agree dates with you in writing before we start.

What you get

A record of every change. A letter that it worked.

Remediation record
  • Every finding and the path chosen for it
  • What changed, where and when
  • Retest result for each fix
  • Anything still open, and why
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.
Change log · your-domain.govSample · 3 of 9
  1. F-01RDP closed to the internetFirewall
    allow tcp/3389 from anyallow tcp/3389 from vpn-users

    Retestpass

  2. F-02Email moved to enforcementDNS
    _dmarc v=DMARC1; p=none_dmarc v=DMARC1; p=reject

    Retestpass

  3. F-04Old TLS versions turned offWeb server
    ssl_protocols TLSv1 TLSv1.2;ssl_protocols TLSv1.2 TLSv1.3;

    Retestpass

Illustrative. Each change is recorded with what it replaced.
Ends with the signed verification letter

Questions

Before you pick a path.

Something else? team@americasecure.com

Yes, and most organizations do. You choose per finding, and you can switch a finding from guided to done-for-you at any point.

Only access to the systems in scope, through named accounts you create and can switch off at any time. Nothing changes until you have approved the change plan.

Yes. That is what the guided path is for. The plan is written for your actual systems, so your vendor can follow it step by step, and we answer their questions along the way.

We tell you exactly what is still wrong, update the plan, and retest again. The verification letter only lists fixes that passed.

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.