File Safer malware scan
- Print
- PDF
File Safer malware scan
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Available in Classic and VPC
If you selected the File Safer integration option when creating a SourceCommit repository, you can use the malware detection feature provided by File Safer. Check the malware of files in the repository using the File Filter feature of File Safer.
Note
- For more information on how to create SourceCommit, see Getting started with SourceCommit.
- For more information on various features of File Safer, see File Safer user guide.
Check scan status
To check the File Safer malware scan status, follow these steps:
- Access the NAVER Cloud Platform console.
- Click Services > Developer Tools > SourceCommit, in order.
- Select a repository from the SourceCommit page and then click the [Go to code] button.
- You can also click the repository name from the repository list.
- Click the [Commit] tab of the Repository's detailed feature page, and then check the FILE SAFER item displayed on the right side of the list.
- The following describes the statuses shown in the FILE SAFER item.
- Not scanned: File Safer scanning is not conducted
- Scanning: scanning of File Safer in progress
- Scanned: File Safer scan completed
- The following describes the statuses shown in the FILE SAFER item.
Request scan
To request File Safer malware scan for the commit, follow these steps:
Note
- You can scan the script and binary files of up to 10 MB by requesting File Safer scan.
- Scan target extensions:
bat
,cmd
,vbs
,vbe
,js
,jse
,wsf
,wsh
,html
,htm
,hta
,jsp
,php
,cgi
,ahk
,au3
,py
,lsp
,fas
,ps
,eps
,gsf
,ps1
,sh
,exe
,dll
,com
,so
,zip
,tar
,gz
,tgz
,rar
,xz
,7z
- You can change the scan target extensions later.
- Access the NAVER Cloud Platform console.
- Click Services > Developer Tools > SourceCommit, in order.
- Select a repository from the SourceCommit page and then click the [Go to code] button.
- You can also click the repository name from the repository list.
- From the Repository's detailed feature page, click the [Commit] tab.
- Find a commit shown as Not scanned in the FILE SAFER item from the commit list, and then click .
- Select the Set scanning target and Set scanning option items in the File Safer scan area of the File Safer result popup window, and then click the [Request scanning] button.
Check scan result
To complete the File Safer's malware scan and check the scan result, follow these steps:
Note
- File Safer's scan result is provided based on the file's hash value, not the repository. So if there's a scan history for the file, the scan result is shown regardless of the repository's location.
- Access the NAVER Cloud Platform console.
- Click Services > Developer Tools > SourceCommit, in order.
- Select a repository from the SourceCommit page and then click the [Go to code] button.
- You can also click the repository name from the repository list.
- Click the [Code] tab of the Repository's detailed feature page, and then check the FILE SAFER item displayed on the right side of the list.
- The following describes the statuses shown in the FILE SAFER item.
- Safe: safe file
- Suspected to be malicious: detected malicious file
- Not scanned: no File Safer scan history
- Scanning: File Safer scanning in progress
- Not target: not a target for File Safer scan
- The following describes the statuses shown in the FILE SAFER item.
Note
- You can scan the script and binary files of up to 10 MB by requesting File Safer scan.
- Scan target extensions:
bat
,cmd
,vbs
,vbe
,js
,jse
,wsf
,wsh
,html
,htm
,hta
,jsp
,php
,cgi
,ahk
,au3
,py
,lsp
,fas
,ps
,eps
,gsf
,ps1
,sh
,exe
,dll
,com
,so
,zip
,tar
,gz
,tgz
,rar
,xz
,7z
- You can change the scan target extensions later.
Was this article helpful?