LinuxSecurity.com
Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Welcome!
Sign up!
EnGarde Community
Login
Polls
What is the most important Linux security technology?
 
Advisories
Community
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
SELinux
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Securitydistro
Latest Newsletters
Linux Security Week: July 28th, 2014
Linux Advisory Watch: July 25th, 2014
Subscribe
LinuxSecurity Newsletters
E-mail:
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

  
Ease the security burden with a central logging server Print E-mail
User Rating:      How can I rate this item?
Source: techrepublic.com - Posted by David Isecke   
Network Security My advice: Don't go another day without setting up a centralized logging server with syslog. Nearly all routers and switches can send log traffic on UDP port 514 in a syslog format. It's just a matter of providing a secure platform to collect that information. I recommend setting up a Linux box to handle this syslog task. It's simple and inexpensive, and it provides data security to some of the most valuable information about your network. . . . Every network device on your network has some type of logging capability. Switches and routers are extremely proficient in logging network events. Your organization's security policy should specify some level of logging for all network devices.

It's important to deny traffic you don't want in your networks, but you also need to know who's sending that traffic. Some resourceful hacker could be hammering away at your outside interface and eating up bandwidth and processes. You need to know where that traffic is coming from. Your access lists should be logging all denied ports and protocols.

But the truth is that admins typically don't log routers and switches. When a problem occurs, we just reboot them or restart an interface, and then chalk it up to a hardware glitch.

My advice: Don't go another day without setting up a centralized logging server with syslog. Nearly all routers and switches can send log traffic on UDP port 514 in a syslog format. It's just a matter of providing a secure platform to collect that information. I recommend setting up a Linux box to handle this syslog task. It's simple and inexpensive, and it provides data security to some of the most valuable information about your network.

Read this full article at techrepublic.com

Only registered users can write comments.
Please login or register.

Powered by AkoComment!

 
< Prev   Next >
    
Partner

 

Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
Ottawa Linux Symposium: May get by with a little help from its friends
Black Hat 2014: How to crack just about everything
NSA Playset, 911 hacked and war cats: A wild ride at DEF CON 22
More Details of Onion/Critroni Crypto Ransomware Emerge
Is there Another NSA Leaker? Updated
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2014 Guardian Digital, Inc. All rights reserved.