Contents x
File Safer malware scan
  • Print
  • PDF
Contents

File Safer malware scan

  • Print
  • PDF

It can be used in a Classic/VPC environment.

If you selected the File Safer linkage option when creating a SourceCommit repository, you can use the malware detection feature provided by File Safer.

Note

Check inspection status

The following describes how to check File Safer malware scan status.

  1. Connect to the NAVER Cloud Platform console.
  2. Click the Services > Developer Tools > SourceCommit menus, in that order.
  3. 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.
  4. In the Repository's detailed features page, click the [Commit] tab, and then check the FILE SAFER item shown on the right of the list.
    sourcecommit-use_fs1_ko
    • The following describes the statuses shown in the FILE SAFER item.
      • Not inspected: no File Safer inspection conducted
      • Running: File Safer inspection in progress
      • Inspection complete: File Safer inspection is complete.

Request inspection

The following describes how to request File Safer' malware scan in the commit.

Note
  • You can scan the script and binary files of up to 10 MB through requesting File Safer inspection.
  • Inspection target extension: 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
  • The inspection target extensions can be changed later.
  1. Connect to the NAVER Cloud Platform console.
  2. Click the Services > Developer Tools > SourceCommit menus, in that order.
  3. 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.
  4. From the Repository's detailed feature page, click the [Commit] tab.
  5. Find a commit shown as Not inspected in the FILE SAFER item from the commit list, and then click i-sourcecommit-filesafer.png.
  6. Select the Set inspection target and Set inspection option items in the File Safer inspection area of the Check File Safer result pop-up window, and then click the [Request inspection] button.
    sourcecommit-use_fs2_ko

Check inspection result

The following describes how to complete the File Safer's malware scan and check the inspection result.

Note
  • File Safer's inspection result is provided based on the file's hash value, not the repository. So if there's a inspection history for the file, the inspection result is shown regardless of the repository's location.
  1. Connect to the NAVER Cloud Platform console.
  2. Click the Services > Developer Tools > SourceCommit menus, in that order.
  3. 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.
  4. In the Repository's detailed features page, click the [Code] tab, and then check the FILE SAFER item shown on the right of the list.
    sourcecommit-use_fs3_ko
    • The following describes the statuses shown in the FILE SAFER item.
      • Safe: safe file
      • Suspected to be malicious: detected malicious file
      • Not inspected: no File Safer inspection history
      • Running: File Safer inspection in progress
      • Not eligible: not a target of File Safer inspection
Note
  • You can scan the script and binary files of up to 10 MB through requesting File Safer inspection.
  • Inspection target extension: 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
  • The inspection target extensions can be changed later.
Was this article helpful?
What's Next