cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
MarcinK
Level 9
Report Inappropriate Content
Message 1 of 8

Best Practice for long ODS scan

Hi,

I'm in the process of scanning the nfs share. This share has 8TB size. This scan takes more than 24 hours. Now after update DAT the ODS Scan Manager Process is stopped and not startet again. I don't know why 😞 . So this scan never ending correct. In the logs aren't information what is possible cause.
This scan is started as Run Client Task Now , not schedule.

I using limit 80% CPU.

How will be best practices for these scan? This will be regular scan at every weekend.

Best regards

7 Replies

Re: Best Practice for long ODS scan

Do you have OAS "Scan when copying from network folders and removable drives enabled"?

Dave

ZeeArhaan
Employee
Employee
Report Inappropriate Content
Message 3 of 8

Re: Best Practice for long ODS scan

Hello,

Yes, there is an option in the OAS policy under the Policy catalog in EPO, which says "Scan when copying from network folders and removable drives." And this option is enabled by default.

Hope this helps.

Best Regards

Was my reply helpful?
If you find this post useful, please give it a Kudos! Also, please don't forget to select "Accept as a solution" if this reply resolves your query!
MarcinK
Level 9
Report Inappropriate Content
Message 4 of 8

Re: Best Practice for long ODS scan

I have this option but I forgot to write that this is the Linux server. All server are LinuxOS.
ZeeArhaan
Employee
Employee
Report Inappropriate Content
Message 5 of 8

Re: Best Practice for long ODS scan

Hello, 

Thank you for reaching out to the Trellix support community.!...

When scheduling your weekly scan, Trellix recommendation as a best practice would be to run a policy based on demand scan. Rather than running "Run client task now" In the Policy based ODS, you can supplement this scan with custom on-demand scans for more targeted scans, such as Memory for rootkits, Running Processes, All local drives, Registry, All mapped drives, All removable drives etc. The main difference is only Policy-based On Demand Scan Tasks for ENS will populate Queries/Reports and return these events.

You may also refer the KB below - Custom on-demand scan task criteria for "All removable drives."

https://kcm.trellix.com/corporate/index?page=content&id=KB96025

Best Regards

 

 

 

 

 

Was my reply helpful?
If you find this post useful, please give it a Kudos! Also, please don't forget to select "Accept as a solution" if this reply resolves your query!
Rfranci1
Level 8
Report Inappropriate Content
Message 6 of 8

Re: Best Practice for long ODS scan

Hi @MarcinK ,

points to note :

1. I hope you have a dedicated machine just for scanning file on demand on the the NFS storage. Becasue taking 24 hours to scan a 8 TB storage is not bad if you ask me . The more files you have the more time it takes to scan and depending on the number archive files you have, the scan time and resource usage (CPU and memory) will also increase. This is expected.

2.Using ODS on a big shared drive is not very secure as you might think. because of the amount of time it takes to scan.
Example : lets say a scan takes 24 hours to complete . If the first scanned file in the initial 5 minutes of scan can be modified even with in the total scan time (24 hours ) and if the file gets infected, then you will have to wait until the next scan schedule starts to detect that file .In your case 1 week.

Because of this reason, it is import to have "Scan when copying from network folders and removable drives" enabled on clients/servers that access files form this share drive. So, the files are scanned every time before it is run. 
So, what i would recommend is to have ODS scheduled as it is now and enable "Scan when copying from network folders and removable drives" .

3. Run Client Task Now - by default has a stop time of 20 minutes for any task and a cancel task option as well. A scheduled task is always recommended .

4. To get information on what files were scanned, you can enable logging through the below steps

  • Login to EPO -> Policy catalog -> Options
  • select the policy name that is applied to the machine. (A test policy is preferred initially that is only applied to the machine in question)
  • click "show advance" . (if needed)
  • Scroll down and enable the option "Log all scanned files during on-demand scans".
  • Save the policy.
  • Now you will be able to see all files scanned by ENS during ODS.

In case if the issue still persists, a screen shot of the issue and logs will be helpful to review . (please morph any sensitive data before posting that info on community )

I hope this helps 😄

- Rohit Francis 

MarcinK
Level 9
Report Inappropriate Content
Message 7 of 8

Re: Best Practice for long ODS scan

Ad.1
I have dedicated server for this scan.

Ad. 2
FIne, but I have only Linux servers

Ad. 3
I changed this time to 99 hours.
I use ODS scheduled task but on the other servers. And I scanning All local drives.

Ad. 4
I used this option 🙂

Re: Best Practice for long ODS scan

What I'm wondering is why not just depend upon OAS rather than ODS? If the server has ENS, and the clients have ENS and scan network access, they will all scan the file before they access them, so what is accomplished by running on ODS?

Dave

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from product experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by employees.
Join the Community
Join the Community