2 Replies Latest reply on Aug 24, 2010 6:15 AM by Nishantha_R

    Development arena

      Hi, we are a software company, and have serious issues within development.

      They complain that the on-access scanner kills a lot of what they are doing. When they compile code or create binaries, naturally the on-access scanner kicks and scans or even qurantines the files they are creating, thus making the whole process massively longer. Some of these guys compile code every 2-5 minutes, yes instead of it taking seconds its taking munites!

      Does anyone have any experience with this kind of setup, and how is the best way to set these guys up with McAfee without intruding on what they do

        • 1. Re: Development arena
          Attila Polinger

          Hello,

           

          just blindly I assume that some of the development occurs in Java. Then I would exclude Java archive files from OAS scanning. In any other cases where similar compressed files are being created by the minute by the compiler, an appropriate exclusion rule could be set up.

          For any other files I would experiment with excluding directories the files are written to. For efficient exclusion definitions please search teh McAfee KB or you can find some threads here having that topic, also.

           

          Attila

          • 2. Re: Development arena

            You have few options here:

            • One option is: You can use low risk process option to specify the process and exclude affected java file types. Then create a regular ODS only for those excluded file types.
            • Another option is: giving them a specific folder for storing their projects and excluding that folder.

            Even you can combine both the above options.