At IT Security Workshop of TeleTrusT, the Federal Association for IT Security e.V., Net at Work contributed significantly to a successful workshop with several contributions.
Advanced Persistent Threat (APT) is a complex attack on IT infrastructures. How to protect yourself from Advanced Persistent Threats?
Last Thursday, the NoSpamProxy team held a workshop with the title “Catch me if you can” at the Vogel IT. In the special location of the RheinEnergie sation in cologne, Stefan Cink ,product manager for NoSpamProxy, demonstrated in real time how simple it is to fool customers, employees and leaders with simulated email addresses and to cause extensive financial damage.
The latest version of our gateway solution NoSpamProxy is now available at „Download NoSpamProxy“. Therewith, you can meet the requirements of your clients insofar as email security in a Microsoft environment even better and easier.
On July 11th, version 12.0.17191.8 was released. This release contains the following fixes and improvements:
On 13th June Version 11 has been released to the public. The new Disclaimer option is the key feature of this version. For the past IT departments had to provide some solutions installed directly on the Mailserver to provide a company wide footer or text signature in mails. This is no longer an issue. With NoSpamProxy you can do this on the central Gateway without the need to add something to your Mailserver.
Of course there has been a lot of improvements to existing features, too. The direct update is supported from 10.x on and will keep all your settings.
Many customers ask how to block certain attachments, especially potentially harmful ones. Here is how it works.
First of all you have to define a ruleset which you want to use. We call it a content filter policy. Select Presettings (1) and Add (2) to create a new one. Give your policy a good name for what it will do. Now you have to define the attachment types you want to give a special treatment. Click Add (3) and create a new definition. Please be aware your definitions are evaluated from top to bottom and first matching entry will be applied. So if you allow invoice_0815-GmbH_*.zip this should be on top of rejecting *.zip-entry.