Showing posts with label Monitoring. Show all posts
Showing posts with label Monitoring. Show all posts

Monday, April 11, 2011

Advanced File Integrity Monitoring for IT Security, Integrity and Compliance: What You Need To Know

Deciding which file integrity monitoring (FIM) product to deploy can be challenging. Unlike many other IT security tools, there are not an overwhelming number of options available. Still, understanding which product is the best for your environment in terms of functionality, security, and usability can be difficult. Knowing what to look for in a solution is the first step in making an informed decision.

Newer file integrity software boasts many improvements over the open-source options available. It also has advanced, capabilities that are simply not available with other commercially available solutions. With FIM required by compliance regulations including PCI-DSS, NIST 800-53 and SANS Consensus Audit Guidelines, the need to understand the current generation of file integrity monitoring software is now more important than ever. This paper will explore current file integrity monitoring capabilities and how file integrity monitoring is used to keep data secure and enterprises in compliance.

How it works

All file integrity monitoring products are essentially comparison tools that keep track of cryptographic hashes of files at different points in time. Hashes are used because they provide a unique "fingerprint" of each file and they can be easily analyzed since they are simply a string of characters. When a file is altered in some way, the hash for that given file changes to a unique new value. A strong hash provides absolute certainty, or non-repudiation, that a file has indeed changed. Integrity checking products use various hash algorithms, along with other file parameters, as a basis for proof that a file has, or has not been altered. However, file integrity monitoring products differ drastically in speed, performance impact, and capabilities in how they accomplish these steps. Advanced solutions such as CimTrak software, utilize innovative technologies that maximize file integrity monitoring performance.

Compliance Drivers

One of the major changes is the trend toward the incorporation of compliance checking and reporting. The impetus for this was the tight correlation between various compliance standards and integrity monitoring. Several well-established compliance standards call for file integrity monitoring to be implemented.

Payment Card Industry Digital Security Standard (PCI-DSS)

The Payment Card Industry Digital Security Standards (PCI-DSS) was the first compliance standard to require monitoring of critical systems that handle payment card data. Section 11.5 specifically requires FIM be implemented to check files in the PCI environment. Given the extremely sensitive nature of payment card data, the ability to ensure the integrity and security of systems that handle it is extremely critical.

NIST 800-53 System And Information Integrity (SI) Guidelines

NIST 800-53 "Recommended Security Controls for Federal Information Systems and Organizations" lays out a framework for U.S. government agencies to safeguard IT systems. While it was developed for government use, it can be applied to any organization as "best practice" guidelines. For this reason, many commercial organizations also adopt the framework. Two main sections, SI-4 and SI-7 of the standard specifically discuss the need for integrity monitoring. Both sections deal with monitoring the IT environment for changes, which could affect security and compromise sensitive information. SI-7 specifically calls for a "... system that detects and protects against unauthorized changes to software and information." It further states that "commercial off-the-shelf integrity mechanisms" should be deployed.

SANS Consensus Audit Guidelines (CAG)

SANS Consensus Audit Guideline #3, Secure Configurations for Hardware and Software on Laptops, Workstations, and Servers, also calls for monitoring to be implemented. SANS Consensus Audit Guideline #3 discusses how deploying file integrity monitoring can detect security threats and notify appropriate personnel in a timely manner. Requirement 3.5 requires integrity checking tools be placed on servers to monitor the security of the operating system as well as applications. CAG requirement 3.7 requires monitoring for critical system files including "executables, libraries and configurations" to ensure that changes are detected and that appropriate IT personnel are alerted.

Key Questions When Evaluating a File Integrity Monitoring Solution

Is the solution capable of truly real-time detection?

Is the solution easy to install, configure and use?

Does the solution only log file changes or does it have other capabilities?

Does the solution give you important information regarding changes such as who made the change, what process was used, and the originating IP address of the change?

Can the solution show you exactly what within a file was changed, giving you a side-by-side comparison with the original file?

Does the solution integrate with other security solutions such as SIEM's?

What inherent security does the solution have?

File Integrity Monitoring plays a critical role in maintaining the security, integrity, and compliance of you organization's IT assets. By providing you key information on changes, file integrity monitoring allows you to be are of, and react to, changes efficiently. Understanding how various solutions differ is the first step in finding and implementing solution that meets your needs. Read more about file integrity monitoring at www.fileintegritymonitoring.com and learn more about advanced file integrity monitoring tools

Sunday, April 3, 2011

SCADA Software - The Ultimate Monitoring And Data Gathering Tool On The Market Today!

SCADA software is a term usually in reference to various control systems. SCADA (Supervisory Control and Data Acquisition) describes various computerized systems which function is: monitoring and controlling infrastructure and industrial and facility processes.SCADA software as: Industrial will pertain to refining, fabrication, production and manufacturing. Infrastructure describes private and public systems such as the treatment of water, wastewater treatment and collection, gas and oil lines, electrical power delivery, military defense sirens, and larger boarder communication systems (cable and phone are examples). Facility process pertains to buildings, ships and airports.

SCADA software has key elements. The machine-human technology is the means in which the information and data can be monitored and manipulated by a human technician. A computer system aimed at supervising and acquiring data and to send control commands. Remote units connecting various sensors and sending data. And infrastructure concerned with the communication between the supervising system and the remote units.A system which uses SCADA software coordinates in real time, but does not control in real time. In simpler terms it will manage and manipulate data in current and dynamic real time, but it won't control the process the data is used for in real time.

This is where DCS software comes into play. DCS (distributed control systems), again, in simple terms can be explained as this: This software is about gathering the data deals with process (as related to that data). DCS is usually deals with operations at one location and SCADA is used for purposes and applications covering a larger geographic area. Again, SCADA software deals with a central system watch over and handles all sites or difficult systems over vast areas. Remote units usually control all actions. As an example, the Remote Unit may control water flow through a treatment plant, but SCADA software will allow technicians to set check points for that flow. Think of it as Remote Units do the action and this software monitors the action. Various apparatus are used for the machine-human relationship. Again, this is an interface in which a human being can see and control a process which SCADA software is monitoring.

As an example, if there is a drainage system emptying water, the operator or technician can see how much water is draining, what water temperature it is at and so on. If the operator notices anything wrong, the drainage can be stopped or altered.A very important element of SCADA software deals with alarms. Since SCADA software is a monitoring system, it will see if alarm requirements are being met, and if there is potential for them not to be met. The alarm can be set by the system itself if certain elements occur or are simply not met, or by the technician or operator.

SCADA software also has a SCADA hardware element and usage. The remote units described before are able to perform tasks and their capability to do so is improving. This allows engineers to implement and design programs to be used on these remote units. Telemetry software is an element of SCADA as it allows remote gathering and reporting of data. SCADA software is now in its third phase and that is like any operating system, it is now networked. This vast and open-ended functionality makes it easier to monitor and distribute data across larger geographical areas.

This will also mean that SCADA software is accessible on the internet and able to be worked with through a variety of virtual networks. This software is a monitoring and data gathering tool used in incredibly large and complex industrial systems and infrastructure. It is a vast and complicated tool responsible for key elements of our everyday life -- from sanitized water coming out of our taps to airports transporting thousands and thousands of people daily.

Thursday, March 24, 2011

Linux Log Monitoring and Watcher - About Watching UNIX Log Files

Linux Log Monitoring and Watching - How can you monitor your Linux log files without having to spend hours writing a script for the task or searching the internet endlessly for a log monitoring solution?

Linux log file monitoring and watching is a duty that is in a different dimension all by itself. It is unique. The reason why I say this is that, log files in Linux often vary in format which makes it difficult for many users/admins to accomplish the task of monitoring their various logs. This is why it is impossible to find one good monitor that can be set up to watch custom log files, which by the way, are very common in UNIX environments.

But what exactly do I mean by "format"? By format, I'm referring solely to the format of the dates on the lines in the logs which is usually at the beginning of each line.

For instance, a typical /var/log/messages file on a Linux server, will look something like this:

[nagios.kedy0:501]
[nagios.kedy0:501] tail -6 /var/log/messages
Sep 18 08:23:51 nagios snmpd[4539]: Received SNMP packet(s) from UDP: [10.10.*.*]:47725
Sep 18 08:23:54 nagios snmpd[4539]: Connection from UDP: [10.10.*.*]:47725
Sep 18 08:24:11 nagios sshd[13078]: Authorized to root, krb5 principal dadmin/root@NETNET
Sep 18 08:24:11 nagios sshd[13078]: permit_root_login: PERMIT_GSSAPI_ONLY method: gssapi-with-mic
Sep 18 08:24:11 nagios sshd[13078]: GSSAPIII authenticated jbowman login accepted
Sep 18 08:24:11 nagios sshd[13078]: Accepted gssapi-with-mic for root from 10.10.*.* port 5345 ssh2
[nagios.kedy0:502]
[nagios.kedy0:502]

Notice the first three columns of each line of the above output. They represent the date and time.

Another log file, usually an application log file (not a system log like the one above), can look like this:

[nagios.kedy0:516] tail -3 /prod/app.log
2011/01/20 14:26:35 UTC [SMTPProper,48088609,69.*.*.*] Receiving message for delivery: from=17777551333@vim.blah.com to=['17777551333@vim.blah.com']
2011/01/20 14:26:35 UTC [-] Attempting 'attach' (promo is False) delivery for 17777551333
2011/01/20 14:26:35 UTC [-] Starting factory
[nagios.kedy0:517]

Again, focus on the columns; in this case, it is the first 2 columns that matter.

The day, month and year are separated with forward slashes and they're numerical. Notice the order they're in. The year comes first, then the month, then the day. Other log files may have the order reversed; with the Day coming first, followed by the month, then followed by the year. Other logs may have the fields separated by hyphens instead of slashes. The scenarios here are endless.

Do you now see how trying to monitor a UNIX linux log can be a hellish task for a UNIX user to take on without the proper efficient tool?

Tuesday, March 1, 2011

Employee Monitoring Keylogger for Mac OS X

Have you been thinking about monitoring the utilization on your office Mac computers?

Whenever you have employees that need to make use of the computers to complete their jobs, you may have difficulties in finding out what they may be performing. This can be specifically possible if they run Mac computers in their personal offices or delete logs before shutting down the office Mac. In this case, random computer checking and surveillance cameras will fail to complete your monitoring work. This is a situation businesses face today.

Employee monitoring devices have become more attractive, affordable and easy to use. Companies see their value in helping to increase security, improve productivity and reduce employee misbehavior, competitive information leaks and liability risks.

The very best choice is Mac spy software for employee monitoring, such as Aobo Mac Key Logger. It runs in stealth mode on the office Mac computers. The Mac Key Logger records all the keystrokes entered, websites visited, chat conversations sent and received and send the logs to you by email or FTP secretly.

For employee computer monitoring on Mac OS X, we suggest that an FTP server be setup on your local network server. Create an FTP account with restricted access and use it as the FTP delivery account for Mac Key Logger to upload the logs.

Employee Monitoring Mac Key Logger Key Features

- Stealthy and undetectable Monitoring

- Record all keystrokes typed on any applications

- Record both-side chat history on iChat/AIM/Adium/Skype/MSN

- Record website visits on the Mac computers

- Record desktop screenshots in a preset interval

- Monitor multiple user accounts on one Mac computer

- Secretly send the logs to your email box or FTP server

- Password protected of the program

- Easy-to-use Key Logger for Mac

Employee Monitoring Mac Key Logger Compatibility

- Fully supports Mac OS X 10.4.x, 10.5.x, 10.6.x

- Universal build (for both Intel and Power PC)

- Supports MacBook/iMac/PowerPC/Mac Mini

It is essential to understand what your employees are making use of your office computers and Internet service for. Employee monitoring work will examine not only the working status but also the communication situation of your staff. Get motion now!

Sunday, February 20, 2011

Digital Sign Management: Learn How SNMP Messaging Improves Network Monitoring

For those who don't recall my last column, Erich Brenn was "The Ed Sullivan Show" performer who impressed me as a young boy for his ability to keep numerous bowls and plates spinning. His feat required a high-degree of attention and some pretty quick feet.

I envision administrators of digital signage networks without the proper tools to be in a similar space as Brenn -constantly running from one display monitor to the next to confirm playback, inspect presentation quality and identify potential problems on the horizon. Unfortunately, for the network administrators, the distance they must cover isn't the length of a dining room table, but rather can be as great as across a mall, a campus or even around the world.

One tool at the disposal of digital signage network administrators is SNMP messaging. The idea behind SNMP is devices on the network -for instance a local digital signage player, whether it's integral to the monitor or a standalone device connected to the display- are equipped with the ability to monitor their condition and alert a central server of problems or potential problems. Local condition monitoring of these devices is done via an agent that reports information via SNMP messaging.

So, for instance, one simple task of an SNMP agent in a digital signage network is reporting. In this example, an agent can be setup to report in to the central server at specific intervals, letting the system and the administrator know that the device is still connected to the network and on. However, if there's a problem and the agent fails to report in at the expected time, the server immediately knows there is a status problem with the device that must be addressed. Communications in the form or an email or text message can be sent to the administrator so the issue can be corrected. SNMP can allow a variety of conditions to be monitored, reported and acted upon. Others might include temperature, moisture and even component-level warnings where available.

While SNMP messaging is a smart way to monitor, report problems and ultimately take corrective actions, it's also stupid. Or, more accurately, SNMP doesn't have the smarts to do anything more or less than the administrator asks.

Thus, if an administrator tells an SNMP agent to report in to the central server every minute with a status report, that's exactly what it will do. If the action that's tied to a failure to report is to send out an email to the administrator every time the device fails to report that administrator may one morning be greeted with literally hundreds of emails reporting the failure of that player on the network. While an annoyance, simple steps like extending the reporting interval can reduce those emails from hundreds to a handful.

SNMP is a valuable tool that digital signage network administrators can use to sidestep emulating Erich Brenn. Another is serial control, which I'll explore in my next column.