With more users and devices being added to your network every day, unified access and central policy control have become critical needs. Your organization isn’t alone.
Attend our next live workshop on May 15th to hear how organizations in education and healthcare rely on Cisco Identity Services Engine (ISE) to provide the identity enforcement and secure access control that allow employees, contractors, students, faculty, and guests (choose the user) to use their own devices on the network. Read More »
This introductory post explains how one of Cisco’s security research groups established a network data collection capability for large amounts of network traffic. This capability was necessary to support research into selected aspects of the Domain Name Service (DNS), but it can be adapted for other purposes.
DNS exploitation is frequently the means by which malicious actors seek to disrupt the normal operation of networks. This can include DNS Cache Poisoning, DNS Amplification Attacks and many others. A quick search at cisco.com/security yields a lot of content published, indicating both the criticality and exposures associated with DNS.
Our research required the ability to collect DNS data and extract DNS attributes for various analytical purposes. For this post, I’ll focus on collection capabilities regarding DNS data. Read More »
Mobile Device Management or MDM is ideal for addressing many challenges inherent to our ‘Bring your own Device’ culture. MDM can help enforce policy for mobile devices but when you look closer, you begin to realize it does not solve everything. The challenge is when we ask our MDM technology to make policy decisions out of context.
Cisco’s Identity Services Engine (ISE) offers centralized policy and network intelligence as an MDM compliment for a complete security solution
This is where Cisco comes in with ISE or the Identity Services Engine. We did a Fundamentals of ISE awhile back that still serves as a great backdrop for getting your head around it. ISE is frequently lauded for its ability to provide a single repository for all the potentially complex rules and regulations we need on our network. The point right now however is ensuring we know where ISE begins/ends in reference to MDM. Neither can act completely alone and accomplish everything most customers are hoping for in a BYOD solution especially. But where do we begin and end?
My friends at Cisco’s TechWiseTV have taken MDM to heart and have offered some keen insight from a geek’s POV (point of view) into MDM. Starting with a primer on MDM, Networking 101: MDM, Jimmy Ray answers the questions on what is MDM and what can it do for my organization in his entertaining and educational white board approach.
We first logged IDS, some syslog from some UNIX hosts, and firewall logs (circa 1999). We went from there to dropping firewall logging as it introduced some overhead and we didn’t have any really good uses for it. (We still don’t.) Where did we go next? Read on.