Comprehensive Guide to Saner Agent Device Scanning and Data Processing

Agent Activation Status 

1. When a device is activated, the agent sends a response code to the Saner server. 
2. Only after receiving this response does the agent appear on the Viser interface as active and ready for operations. Align agent versions with organizational policies or compliance requirements. 

Compliance Scan 

1. The compliance scan is initiated using a predefined command: 
   "C:\Program Files (x86)\SecPod Saner\Agent\6.3.1.4\bin\spscanmanager.exe" COMPLIANCE "C:\Program Files (x86)\SecPod Saner\Agent\6.3.1.4" "C:\Program Files (x86)\SecPod Saner\Agent\6.3.1.4\updates" 
   
   
2. After execution, the agent verifies the scan's exit code to confirm successful completion. 
   Scan process exit code for 'COMPLIANCE' scan. Exit_code:The operation completed successfully.
   
   
3.  The system logs an entry similar to the following: 
    

1. Upon completing the compliance scan, the agent automatically starts the vulnerability scan using the following command: 
   "C:\Program Files (x86)\SecPod Saner\Agent\6.3.1.4\bin\spscanmanager.exe" VULNERABILITY "C:\Program Files (x86)\SecPod Saner\Agent\6.3.1.4" "C:\Program Files (x86)\SecPod Saner\Agent\6.3.1.4\updates" 
2. Once the scan is finished, logs are updated and can be accessed on the Viser device page. 

• Example log entry: 
   

• After completing the scan, the agent sends a status update to the server. 
  "Updating status to server: ScanDone" 

• This ensures the latest scan results are recorded, and the device's compliance status is updated. 
  Simultaneously, the spscanmanager file is updated with a timestamp. 
   

• The agent executes a command to retrieve detailed scan results, which provide extensive system information. 
  "C:\Program Files (x86)\SecPod Saner\Agent\6.3.1.4\bin\spscanmanager.exe"  "C:\Program Files (x86)\SecPod Saner\Agent\6.3.1.4" 
   

• These results are then uploaded to the server with a confirmation message, ensuring the latest device insights are available for analysis. 
  Scan process exit code for 'Detailed System' scan. Exit_code:The operation completed successfully. 
   

• The patch scan is triggered using the following command: 

• Upon successful execution, logs capture the details, and completion messages confirm the process. 
  installed and missing patch collection done 
  ScanDone status. Successfully updated to server. 
   

• The agent downloads CDT (Configuration Data Template) files from the server using the following command: 

• These files help ensure accurate assessment and scanning of the device’s security posture. 
  getAllCREs DONE!!  
  All cre files downloaded. 
  
  

• The agent verifies available updates for Windows Update Agent (WUA). 

• Logs capture probe collection, system information gathering, and installed patches. 
   

• The agent collects patch repository data using the following command: 

• Logs indicate successful repository collection and scan completion.