Exlusions on CyberCapture for entire folder?

[DavidR]

Reply from the devs: He needs to make sure that he has \* at the end of the path to ensure the exclusion works such that if I want to exclude all files in D:\test I need to add exclusion as D:\test\*

So this I take it is also confirmation that the CyberCapture function doesn't only dealt with executables downloaded from the internet and has been expanded ?

If so it would be nice to know its scope now, what files and areas are covered ?

[Asyn]

DR: First of all it is not CyberCapture, but DeepScreen (sandbox)

[DavidR]

DR: First of all it is not CyberCapture, but DeepScreen (sandbox)

Pretty damn confusing then having the "CyberCapture" Blue tab at the top of the window.

[Lisandro]

I've got the following official clarification:

Deepscreen (sandbox) is now also called CyberCapture (it's displayed in the blue border around scanned app's windows). It's because both DeepScreen and CyberCapture are enabled/disabled by the same checkbox in the UI. So the user's issue is that the files are getting into Deepscreen rather than CyberCapture.

[DavidR]

Thanks for that.

Should we also be changing the DeepScreen reference in the avastUI > Settings > Exclusions and calling it CyberCapture to avoid confusion.

Also we still don't have clarification on the expansion of CyberCapture scans as it would appear it doesn't only dealt with executables downloaded from the internet and has been expanded.

It would be nice to know its scope now, what files and areas are covered ?

[Lisandro]

Thanks for that.

Should we also be changing the DeepScreen reference in the avastUI > Settings > Exclusions and calling it CyberCapture to avoid confusion.

Also we still don't have clarification on the expansion of CyberCapture scans as it would appear it doesn't only dealt with executables downloaded from the internet and has been expanded.

It would be nice to know its scope now, what files and areas are covered ?

Only downloaded PE (portable executables).

[DavidR]

Thanks for that.

Should we also be changing the DeepScreen reference in the avastUI > Settings > Exclusions and calling it CyberCapture to avoid confusion.

Also we still don't have clarification on the expansion of CyberCapture scans as it would appear it doesn't only dealt with executables downloaded from the internet and has been expanded.

It would be nice to know its scope now, what files and areas are covered ?

Only downloaded PE (portable executables).

Then someone has to answer how/why it was scanning a 'local' visual studio file as in the OP's image in Reply #10.

Whilst Asyn is suggesting that this is DeepScreen (in sandbox) at work at the very lease it is confusing users. Even more so when there is no mention of DeepScreen in the General or Components section of avast settings.

[Asyn]

Should we also be changing the DeepScreen reference in the avastUI > Settings > Exclusions and calling it CyberCapture to avoid confusion.

Hi Dave, it has been changed already.

PS: DR is short for dev-reply.

[DavidR]

Should we also be changing the DeepScreen reference in the avastUI > Settings > Exclusions and calling it CyberCapture to avoid confusion.

Hi Dave, it has been changed already.

PS: DR is short for dev-reply.

1. Good - thanks, it certainly needed action.
2. I gathered that, but as we haven't seen anyone posting the new change, it was just hanging in limbo.

[Asyn]

Good - thanks, it certainly needed action.

You're welcome.