The Bring Your Own Device (BYOD) phenomenon has become a highly debated topic in many organizations. While some enterprises are fully enveloped in the BYOD trend, others are hesitant to adopt this new strategy because of the numerous risks associated with it. Regardless, here is what you need to know to be BYOD-ready.
On May 23rd, Nikos Mavrogiannopoulo (one of the primary authors of the GnuTLS library) submitted a commit identifying the potential for “memory corruption” during the TLS/SSL handshake process. This specific bug makes it possible to initiate a server-based attack on a client system by corrupting its memory using a specially crafted ServerHello message.
By now you’ve probably heard about a major vulnerability in the OpenSSL Project’s implementation of SSL known as Heartbleed. If you’re not familiar with SSL, it is a protocol designed to secure communication between an end-user (client) and application (server) using cryptography and keys intended to make it difficult to intercept and read protected traffic. The process of establishing that secure communication looks something like this:
Saar here, resident engineer at Myriad Supply. Today I’ll be discussing DDoS ammunition.
The FFIEC gives “recommendations” to banking institutions. This is a non-binding recommendation, and there is no law per say that says you must have DDoS protection. However, if someone suffers financial damages due to a DDoS attack on a bank, that person can hire an attorney who can then prove that the bank handled itself without due diligence in spite of government recommendations. So a reasonable judge will find the bank at fault and it would have to pay. Add a class action, and you’re looking at a pretty hefty sum. In this article for example, http://www.scmagazine.com/banks-file-class-action-against-target-and-trustwave-over-massive-breach/article/339760/, the banks are suing Target for failing to have decent security, which cost them millions replacing stolen payment cards.
In the WiFi world, there are three major types of wireless deployments. These are, as the title says, Controller Based, Cloud Managed, and Standalone; They are all different, and each one has its correct application, benefits, and vices. It has come to my attention that the differences among these groups aren’t understood well. Usually people are more interested in the brand name rather than the group it falls in. And that’s okay, I am here to help you choose the correct WLAN solution for your needs. Just to clarify, I will NOT be going into a discussion of which manufacturer falls into which category, or which one is better. That type of battle is best left alone for another day.