How to Conduct Salto System Audits
Table Of Contents
How Do You Conduct a Salto System Audit?
You conduct a Salto system audit by reviewing access data, hardware status and user records in a structured sequence. The audit begins with a full export of the audit trail from the Salto management software. The export captures every door event, credential use and system change across the site. A technician then checks each reader, handle and controller against the recorded events. The comparison reveals doors with no logged activity, which signals a fault or an offline unit. The audit continues with a review of user permissions against the current staffing list. Any credential assigned to a departed person becomes a finding for immediate removal. The final stage documents every fault, gap and correction in a written audit report.
The conduct of a Salto system audit demands a methodical order of steps. A random or partial review hides faults that a full sequence exposes. Start the audit at the main entrance, then move through each zone in building order. Test one door at a time, and record the door name before any check begins. Log the serial number of each reader and controller during the physical inspection. Match each serial number to the entry in the Salto software database. A mismatch between hardware and software records points to a swapped unit or a missed commissioning step. Photograph any damaged reader, loose handle or exposed wiring as evidence. Close the audit with a summary that ranks findings by risk level.
What Preparation Does a Salto System Audit Need?
Preparation for a Salto system audit needs a current site plan, a credential list and software access. The site plan marks every door fitted with a Salto reader or electronic cylinder. The credential list names every card, fob and mobile key holder on the system. Software access means a login with administrator rights to the Salto management platform. An administrator login allows the export of complete audit trails and user databases. A technician also prepares a test card set before the audit starts. The test card set includes one valid credential and one deliberately expired credential. The pair of test cards verifies the reader response at every door. A charged tablet or laptop records findings on site during the inspection.
Preparation also needs a schedule that avoids disruption to normal building operations. Book the audit outside peak entry periods, such as shift changes or opening hours. Notify staff and tenants about the audit dates, so test swipes cause no alarm. Confirm the availability of the server or encoder room before the audit begins. A locked server room delays the software checks and stretches the audit timeline. Gather previous audit reports and maintenance records into one folder. The previous reports show recurring faults and unfinished corrective actions. A prepared checklist keeps the audit on track and prevents missed doors. The checklist lists every door, every test and every record check in order.
Which Records Belong in a Salto System Audit?
The records that belong in a Salto system audit include audit trails, user databases and event logs. Audit trails list every credential swipe, denied entry and door release across the site. The trails show the exact time, door name and credential holder for each event. User databases record the name, access level and issue date of every credential. The databases expose cards still active for people who left the organisation. Event logs capture system faults, battery warnings and communication failures at each door. Maintenance records document past repairs, firmware updates and battery replacements. The maintenance records confirm whether a fault received a permanent fix or a temporary patch. A complete audit file combines all five record types in one report.
Each record type answers a different audit question, so the audit needs all of them. The audit trail answers questions about door activity and unusual entry patterns. A door with zero swipes over several months signals a broken reader or a closed area. The user database answers questions about permission accuracy and credential hygiene. An access level granted to fifty people, where the role needs five, flags excessive rights. The event log answers questions about hardware health and network reliability. Repeated offline warnings at one door point to a failing controller or a weak connection. Filing the records together creates an evidence trail for compliance reviews. The evidence trail supports insurance, security certification and internal governance requirements.
How Do You Test Salto Credentials During an Audit?
You test Salto credentials during an audit by swiping a valid card, an expired card and a revoked card at each door. The valid card opens the door, and the software logs the event within seconds. The expired card fails to open the door, and the software records a denied entry. The revoked card also fails, which proves the deletion reached the door controller. A door that accepts a revoked card carries a sync fault between software and hardware. The tester repeats the three swipes at every reader on the site. The repetition confirms consistent behaviour across all doors and access levels. Each test result goes into the audit sheet beside the door name.
The test extends beyond simple swipes to cover special credentials and modes. A master card opens every door, so the audit verifies the master list stays short. A timed credential opens a door only inside set hours, so the tester swipes outside the window. The outside-hours swipe fails, which confirms the time zone setting works correctly. An office mode door stays unlocked during business hours, so the tester checks the schedule against the software. A blocked mode door refuses all credentials, so the tester confirms the block applies to the right doors. Mobile keys on phones receive the same three-swipe test as physical cards. The complete test set proves every credential type behaves as configured.
What Steps Follow a Completed Salto System Audit?
The steps that follow a completed Salto system audit start with a written findings report. The report lists every fault, every permission error and every hardware issue found on site. Each finding carries a risk rating, a recommended fix and a target completion date. High-risk findings, such as a revoked card that still opens a door, receive immediate action. The system owner deletes the stale credential from the software the same day. Medium-risk findings, such as a slow reader, enter the maintenance schedule within the month. Low-risk findings, such as a worn label, join the routine servicing list. The report goes to the system owner and the maintenance provider for sign-off.
The next steps involve corrections, verification and a follow-up schedule. A technician applies each software correction, such as permission removals and time zone fixes. Hardware faults receive repairs or replacement parts according to the report recommendations. After the corrections, a verification check repeats the failed tests from the original audit. The verification check proves each fix produced the intended result. The system owner then books the next audit at a fixed interval. A twelve-month interval suits most commercial sites with stable staffing. A six-month interval suits sites with high staff turnover or sensitive areas. The completed report and the verification record stay on file for the next audit cycle.
How Often Should You Schedule a Salto System Audit?
You should schedule a Salto system audit at least once every twelve months for a standard commercial site. The annual schedule catches credential build-up, battery decline and firmware gaps before faults spread. A site with high staff turnover needs an audit every six months. Frequent departures create stale credentials faster than an annual cycle clears them. A site with sensitive areas, such as server rooms or cash offices, also benefits from a six-month cycle. The shorter cycle limits the window in which an unrevoked card stays active. A small site with stable staffing and few doors manages well on an annual schedule. The schedule suits the risk level, the door count and the staffing pattern of the site.
Extra audits become necessary after specific trigger events on the system. A security incident, such as a lost master card, triggers an immediate full audit. A major software update triggers an audit to confirm settings survived the upgrade. A change of security manager triggers an audit to verify the permission structure under new oversight. An expansion that adds new doors triggers an audit of the extended zone. A power outage or network failure across the site triggers a check of controller logs. Each trigger audit focuses on the affected area and the related records. The trigger audits sit alongside the regular schedule, not in place of the schedule.
FAQS
How long does a Salto system audit take?
A Salto system audit takes one to three days. The duration depends on the door count. The number of credentials affects the audit length. The state of the records also influences the audit duration. A site with clean records finishes faster. A site with working hardware finishes faster. A site with many faults needs extra time for testing. Faulty sites also need extra time for documentation.
Who performs a Salto system audit?
A licensed security technician or an accredited Salto service provider performs a Salto system audit. The technician needs administrator access to the Salto software and knowledge of access control compliance. An in-house system administrator handles the record reviews. The physical door tests and hardware inspections need a qualified technician.
What tools does a Salto system audit need?
A Salto system audit needs a laptop with software access, a test card set, a site plan and a checklist. The laptop exports audit trails and user databases. The test card set verifies reader behaviour at every door. The checklist tracks each door, test and record check to completion.
What happens if an audit finds a revoked card still works?
A revoked card that still works signals a sync failure between the software and the door controller. The technician forces a firmware update or a re-sync at the affected door. The technician then retests the card at the door. A passing retest confirms the fix. The finding receives a high risk rating in the report.
Does a small business need a Salto system audit?
A small business with a Salto system still needs a periodic audit. A small site holds fewer credentials, but stale cards and battery faults appear at the same rate per door. An annual audit with a shortened checklist covers the smaller door count. The audit keeps permissions accurate and hardware reliable.
Related Links
Understanding the Importance of Auditing Salto SystemsCommon Causes of Audit Failures in Salto Systems
Benefits of Professional Audits for Salto Systems
Top Tips for Conducting Audits for Salto in Perth
Common Signs You Need a Salto System Audit