Cybersecurity has always been an evolving challenge for IT teams—even before the pandemic and subsequent mass exodus to the home office. At the Protect & Streamline Summit for IT Leaders, experts from the IT and cybersecurity space came together to share advice for IT leaders scrambling to contend with a new set of business risks. Read on for key takeaways or access all session recordings for a deeper dive.

A few years ago I wrote a blog article about the zero-trust network security model and why I thought it was something every organization should be thinking about implementing. While I still believe that to be true—probably more true than ever, in fact—the landscape since then has changed a great deal, particularly because of the increase in cloud-based services, and zero-trust is now an extremely achievable goal.

In today’s world, it isn’t always practical or possible to be on site to troubleshoot every network issue that pops up. Whether you’re under mandatory stay-at-home orders because of a global pandemic, in the middle of a surprise snowstorm, or sleeping cozy in your bed 60 miles away, being able to access remotely the network would make your life infinitely easier. With Auvik’s remote management features, it’s possible.

When you work in IT, there’s never a shortage of things to do. For folks who like to be busy, IT is a great place to be. But the workload can quickly become overwhelming, and it may often feel like you and your team are putting out fires and not productively working on other tasks that move the needle for your team or company. The trick is managing your team’s time effectively so the excessive pile of work gets done. These four time management strategies can help. Let’s get started.

Let’s be honest: As a network manager, you’re responsible for knowing a little bit about everything when it comes to computer networking. From fundamentals to anticipating future tech changes, there’s a lot of ground to cover. To keep up, you need to keep learning. If you’re wondering where to start, this list of 10 computer networking books can help.

In my previous article, I explained what syslog is and why it’s used. In this article, I’m digging into how to configure syslog on network devices. The explanations and examples will be a bit Cisco specific, mainly because that’s the gear I’m most familiar with. Essentially every modern network device has at least some syslog capabilities, though.

“My computer’s not working!” “I can’t connect to the internet!” “My emails aren’t sending!” You’re probably used to hearing common requests and complaints like these from end users. It’s our job to take these issues, troubleshoot them, bring them to root cause, and get the user back up and running as quickly as possible.

When it comes to cybersecurity, the landscape is constantly changing: the number of cyberattacks is always on the rise, the attacks themselves are becoming more sophisticated, and there’s a serious skills shortage in the industry. There’s a lot to learn about cybersecurity if you want to keep up and keep your users protected.

As a network evolves over time, new devices are added, old devices begin to show their age, and some devices are completely forgotten about. It’s a natural consequence of mergers, upgrades, staff turnovers, and other common occurrences that contribute to redundancy or excess complexity in IT infrastructure.

Syslog is a good thing. It’s a standard network based logging protocol that works on an extremely wide variety of different types of devices and applications, allowing them to send free text-formatted log messages to a central server. Essentially every device on your network—whether it’s a storage box or a server, a switch or a firewall—likely has a syslog agent you can use to send messages to a common central location. People who are familiar with SNMP might be a little confused.