Kapersky Firewall

[SalesServiceGuy]

Does anyone have any experience in configuring a Kapersky firewall to allow a scan to folder on a local PC.

Kapersky Small Office Security V4 running on a Win 10 Home PC.

I know that I have configured the scan path correctly on the copier because when I turn the firewall off, the scan is successful. When I turn the firewall on, the scan is blocked.

There are many other buttons in the Kapersky control panel to change but via trial and error I narrowed the problem down to just the firewall toggle on/off.

Any ideas?

Thanks,

[SalesServiceGuy]

Re: Kapersky Firewall

I searched the forum and found this answer.

"open kaspersky/settings/firewall/settings/network tab/ right click on your network and select trusted network, click ok twice. then kaspersky/settings/firewall/settings/packet rules/right click on TCP and set it to allow click ok. then right click on UDP click allow. You're kaspersky will now allow SMB scan traffic. "

I will give it a try.

Credit to 3BoyDad on the Konica Minolta forum.

[rthonpm]

Re: Kapersky Firewall

For any PC behind a NAT router, there's no real reason for a firewall beyond the standard Windows one. It took me several years to get some of my customers to grasp this concept, but after they saw the amount of issues with things like SMB connections and also much less taxing of system resources with no real loss in security, they relented.

One good way to prove the point is to have the customer turn off the firewall and go to grc.com and use the Shields Up tool to have their computer scanned for any open ports. If they're properly behind a NAT router, i.e. not connected directly to their modem, they are already protected without the additional bloat.

As important as security is, it's filled with all kinds of snake oil, and workstation firewalls are on of the biggest examples.

[SalesServiceGuy]

Re: Kapersky Firewall

You are providing several useful new concepts that I have never heard of before.

Unfortunately, when I arrive at the customer's office they have already made decisions about their network security and there is little upside for me to try and convince them to make a change.

[rthonpm]

Re: Kapersky Firewall

You are providing several useful new concepts that I have never heard of before.

Unfortunately, when I arrive at the customer's office they have already made decisions about their network security and there is little upside for me to try and convince them to make a change.

I'm more on the IT side of the house now, but I still do a good amount of MFP support. It can take time to make customers see the error of their ways, especially when there are licensing costs and other external factors involved. Overall, the biggest error I find is that security is set with the endpoint level far too high, and the infrastructure level far too low. By the time your security policy reaches the endpoints everything should start to have a lighter touch. Your firewalls should be at a level before the patch cable out of the walls. If actual endpoints need to be separated from the general network that's where things like managed switches and VLAN's come into play, but that gets into another ream of cost that usually can be paid for by the waste of workstation firewalls and terrible AV products.

[Ratchet2501]

Re: Kapersky Firewall

Read an interesting bit from Microfail this morning about the whole AV aspect of windows 10. Can't say I remotely approve but *shrugs*

https://blogs.technet.microsoft.com/mmpc/2017/06/20/partnering-with-the-av-ecosystem-to-protect-our-windows-10-customers/