Latest news
Requirements Overview
The first step in designing the log monitoring system is to evaluate the PCI requirements and determine which ones would be in scope. The detailed requirements list from the PCI DSS 1.1 is given in the sidebar. The requirements that might be satisfied with a log monitoring system include:
10.1 – Logging is enabled and active – We need to incorporate these sub-requirements into our log monitoring system design.
10.4 – Time Synchronization – We would need to configure the log monitoring servers to use the same NTP source as the log clients.
10.5 – Audit trail security – We need to incorporate these sub-requirements into our log monitoring system design.
10.6 – Log Review – We can incorporate these sub-requirements into our log monitoring system design.
10.7 – Log Retention – We can incorporate these sub-requirements into our log monitoring system design.
Note that 10.2 and 10.3 would be out of scope for the log monitoring system as these specify the types of events and the metadata that would be recorded. Obviously log content and generation would need to be configured appropriately at each monitored device.
Design Concepts
Now that we know what we’re trying to achieve, let’s examine the possible design concepts and ways in which we can meet the requirements. Perhaps the best way to start is by including a centralized log server in the design. Although only sub-requirements 10.5.3 and 10.5.4 specifically calls for a log server, we’ll see that using the centralized design will allow us to be more flexible in meeting the other requirements and will also only require minimal changes to the production servers in the PCI network.
If you have a geographically distributed network, then you should take the quantity of log traffic into account. Assuming the default syslog protocol is used (as opposed to newer, more enhanced protocols such as syslog-ng) the log messages will be UDP based and could be discarded when WAN traffic is heavy. Therefore, you will probably want to distribute your log monitoring system with at least one log server per datacenter. This will reduce the amount of WAN traffic to a minimum. Don’t forget to configure your wireless APs to communicate with the centralized log server in order to satisfy requirement 10.5.4!
Spotlight

Is it time to professionalize information security?
Posted on 23 May 2013. | The issue of whether or not information security professionals should be licensed to practice has already been the topic of many a passionate debate.

Review: Logging and Log Management
Posted on 22 May 2013. | Every security practitioner should be aware of the overwhelming advantages of logging and perusing logs for discovering system intrusions. But logging and log management comes with its own set of difficulties.

Experts highlight top data breach vulnerabilities
Posted on 22 May 2013. | Hidden vulnerabilities lie in everyday activities that can expose personal information and lead to data breach, including buying gas with a credit card or wearing a pacemaker.

A closer look at Mega cloud storage
Posted on 21 May 2013. | Once a novelty, nowadays many cloud storage services are fighting for their piece of the market in the virtual world. Mega offers 50GB of free space with great pricing on Pro accounts.

The CSO perspective on healthcare security and compliance
Posted on 20 May 2013. | Randall Gamby is the CSO of the Medicaid Information Service Center of New York. In this interview he discusses healthcare security and compliance challenges and offers a variety of tips.
By subscribing to our early morning news update, you will receive a daily digest of the latest security news published on Help Net Security.
With over 500 issues so far, reading our newsletter every Monday morning will keep you up-to-date with security risks out there.





