ARN Smart Support
Language: English

First steps after the security setup

Updated 4 Nov 2026 4 min read
Browse SiteWatch articles

After the security setup, follow these steps once. They give you a first complete report, a working report email and a safe path from observing to blocking.

Make sure the licence is active and a security approver is designated first. See Complete the security setup.

1. Run your first scan

  1. Open ARN SiteWatch → Dashboard.
  2. Under Scan & reports, choose Full code scan and click Scan now. Scans only read files; nothing is changed.
  3. Follow the progress line. You can leave the page: the scan continues through WordPress scheduled tasks. Keeping the page open makes it go faster. Use Cancel scan to stop it.
  4. When the scan finishes, the stored report opens on the Dashboard.

Start with the Executive summary. The Review index (0 to 100) shows how much review work the report contains; it is not the chance that your site is infected. Then open the findings with their evidence. See Run scans and investigate findings.

After the first complete scan, Changed files scan is enough for routine checks.

2. Compare files with official references

Open Site Protection → File Integrity and click Compare core & imported references. SiteWatch compares WordPress core with the official checksums and supported public plugins with their WordPress.org references. See Check file integrity, repair and quarantine files.

3. Look up published vulnerabilities

Open Site Protection → Vulnerabilities and click Refresh vulnerability data. The comparison runs in the background. See Vulnerabilities and hardening.

4. Set up report email

  1. Open Settings → General & Report SMTP.
  2. Check the Report recipient. New installations use the WordPress administrator email.
  3. Under Independent report transport, keep Independent SMTP (recommended) and enter the SMTP hostname, Port, Encryption, From address, SMTP username and SMTP password of a separate mail account.
  4. Click Save settings.
  5. Go back to the Dashboard and click Email this report.
  6. Check that the message really arrives in the recipient's inbox, not only that the service accepted it.

When the test message has arrived, turn on Enable a daily full scan and email its report and, if you want, Send a separate alert when a completed scan detects new high priority findings. See Scheduled reports, alerts and retention.

5. Choose who must use two-factor sign-in

In Access Security → Two-Factor Authentication, choose the roles that must verify their sign-in and the verification method. Make sure the accounts in those roles can enroll first. See Set up two-factor sign-in verification.

6. Observe first, then block

The setup profile puts request patterns, endpoint limits and the email policy in Observe mode. For a few days of normal use:

  1. Sign in and out, submit your forms, place a test order if you run a shop and send password reset and registration emails.
  2. Editors and authors should save posts as usual. Their content is inspected too.
  3. Review the recorded matches in Reports & Events → Event History and on Monitoring → Live Security Events.
  4. Only then switch a policy to Block, one at a time, and test the same workflows again.

See Request patterns, endpoint limits and early protection and Spam controls, email policies and mail diagnostics.

7. Choose pages to monitor

In Monitoring → Site & Asset Health, enter up to five public page paths, such as your home page, a post and a product page, and click Save monitoring policy. Then click Check pages & assets now. See Monitor public pages and assets.

A practical daily review

  1. Check the latest completed report on the Dashboard and its date.
  2. Read high-priority findings with their evidence and coverage limits.
  3. Review pending account and plugin decisions with the security approver.
  4. Check failed notifications, PHP errors and health check results.
  5. Investigate unexpected file changes with official references and an independent backup.
  6. After a planned change, test the affected visitor journey.

Blocked login attempts, budget limits and plugin review holds are recorded policy actions. They are not necessarily attacks.

On this page

Submit a ticket

Create a new support request without needing a portal account.

Priority
Attachments
Only you and our staff see a ticket. Never send passwords or licence codes.

Track a ticket

Use the ticket number and password from your confirmation email.

The number and the password are in your confirmation email.

Sign in

Access your support portal account.

New here?

Create account

Create your support portal account.

Already have an account?

Forgot password?

We email you a link to choose a new password.

Conversation

Was this helpful?
Open full article
↑ ↓ to moveEnter to openEsc to close