Security Checklist
A practical guide to securing the PCs, laptops, and virtual desktops running your Automize RPA bots.
Your RPA bots run on your own infrastructure. This means you are responsible for ensuring that the devices they run on are secure.
Use this checklist to make sure your environment meets the minimum security standards required for safe bot execution.
1. Operating System & Software Hygiene
Windows / macOS / Linux
- Ensure the operating system is fully updated (latest security patches).
- Enable automatic updates wherever organisational policy allows.
Installed Software
- Remove unused or outdated applications.
- Keep browsers and extensions updated (Chrome, Edge, Firefox, etc.).
- Ensure Microsoft Office, PDF readers, and other productivity tools are current.
2. User Access & Account Controls
User Accounts
- Use a dedicated bot account for running Automize RPA (least-privilege access).
- No shared accounts.
- Disable local admin rights for everyday users.
Password Policies
- Enforce strong password rules:
- Minimum 12 characters
- Mix of upper/lowercase, numbers, symbols
- Require password rotation every 60–90 days (or according to internal policy).
- Enable account lockout after failed login attempts.
Session & Screen Lock
- Auto-lock screens after 5–10 minutes of inactivity.
- Require password or MFA to unlock.
3. Endpoint Security
Antivirus / Endpoint Protection
- Ensure a reputable antivirus or endpoint protection suite is installed.
- Keep virus definitions updated daily.
- Enable behavioural threat detection (EDR, XDR).
Firewall
- Ensure the local firewall is enabled.
- Block all inbound traffic except what is required for business use.
- Allow outbound connections only to required destinations (e.g.,
https://automize.co.za).
Malware Protection
- Enable ransomware protection features (Controlled Folder Access / FileVault / Linux equivalents).
- Disable autorun for removable media.
4. Full-Disk & File-Level Encryption
Device Encryption
- Enable full-disk encryption on all machines:
- Windows → BitLocker
- macOS → FileVault
- Linux → LUKS
Sensitive Files
- Encrypt folders containing:
- Credentials
- Logs
- Temporary bot outputs
- Use AES-256 or equivalent encryption.
5. Network Security
Wi-Fi / LAN
- Avoid public Wi-Fi.
- Require WPA2-Enterprise or WPA3 encryption.
- Guest networks should be isolated from corporate networks.
VPN Requirements
- Require VPN for remote staff before bot execution.
- Enforce MFA on VPN logins.
Proxy & Filtering
- Ensure bots can reach Automize services by whitelisting required domains.
- Block malicious categories (torrents, unknown sites, etc.).
6. Secure Credential Handling
Storage
- Store credentials only in:
- Automize’s secure vault
- Windows Credential Manager
- Approved enterprise password vaults
Never store credentials in:
- Notepad
- Excel sheets
- Emails
- Sticky notes
- Browser autofill (disable this)
Multi-Factor Authentication
- Use MFA wherever supported.
7. System Hardening
Minimum Requirements
- Disable unnecessary services (Bluetooth, Remote Desktop, SMBv1).
- Enforce strong UAC settings.
- Restrict PowerShell execution (where policy allows).
- Enable audit logging (successful + failed logins).
Bot-Specific Hardening
- Ensure bot machines are not used for personal browsing or unrelated work.
- Restrict access so only authorised staff can log into bot machines.
8. Backup & Recovery
Backups
- Implement daily incremental backups and weekly full backups.
- Backup logs and bot configurations securely.
- Ensure backups are encrypted.
Recovery
- Test restore procedures at least twice per year.
- Store at least one backup copy offline (“air-gapped”).
9. Physical Security
- Ensure laptops and desktops are kept in secure areas.
- Lock rooms where bots run unattended.
- Use Kensington locks where practical.
- Never leave bot machines logged in and unattended.
10. Compliance Requirements
Ensure compliance with:
- POPIA
- GDPR (if applicable)
- Internal Information Security Policies
- Industry-specific frameworks (ISO 27001, PCI-DSS, etc.)
Document all measures taken, and retain proof for audits.
11. Pre-Go-Live Security Self-Assessment
Before allowing Automize RPA bots to run in production, confirm:
| Item | Status |
|---|---|
| OS updated | ☐ |
| Antivirus active and updated | ☐ |
| Firewall enabled | ☐ |
| Full-disk encryption enabled | ☐ |
| Dedicated bot user created | ☐ |
| MFA enabled on all accounts | ☐ |
| VPN required for remote access | ☐ |
| Credential vault configured | ☐ |
| Logs protected and access-controlled | ☐ |
| Device physical security in place | ☐ |