AV Scanning of transported files

QUESTION: Are files uploaded or in transport scanned for viruses?

ANSWER: We are fully encrypting data, which means that we would need to unencrypt (at some point) the payload in order to scan it.  Couple of issues that our customers have with this: 1. Customers don’t want Botdoc having access to their data, neither do we want the liability of being able to see their data.   2. Botdoc is a real-time, remote, adhoc Transport technology. Depending on the size of the payload, the scanning process would delay the delivery of the data to the intended recipient.  

FYI - With our API (that is built into large existing systems), when data comes back into the system that requested it, most of our customers choose to use their own internal scanning tools as those are good practices before allowing anything to be put internally to their systems. A common architecture used is once any file/data is ready to be retrieved from Botdoc, our Customers send this data to a separated Bucket (storage). Once it's added it gets automatically scanned by our customers local systems in place for this task. Once the file/data is cleared, the same is moved to its final destination internally to the system integrating Botdoc.  

With all of this said, this capability remains on our roadmap and we continue to ponder what it would look like to build some type of scanning into the Botdoc NOW product, without adding friction (i.e. time) and/or security issues to the mix. 

What we suggest is a ‘local’ scanning technology of some sort, most of our clients use Cylance, inexpensive and market leader.  

FULL VIEW CLICK HERE