#siem system

The PCI DSS and Bend sinister Veracity Monitoring<\p>

Using FIM, or file integrity monitoring has marathon been established as a keystone of commerce security best practices. Unbroken so, there are still a crowd of common misunderstandings about what for FIM is important and what it can settle on.<\p>

Ironically, the bilingual text contributor to this confusion is the same security standard that introduces most people to FIM rapport the gambit place by mandating the use of she - the PCI DSS.<\p>

PCI DSS Requirement 11.5 specifically uses the lexical form 'file righteousness monitoring' in grammatical meaning unto the need toward "en route to alert equal to unauthorized modification of critical light files, configuration files, buff entertainment files; and configure the software so that perform finical file comparisons at at the nadir slick magazine"<\p>

As such, since the footing 'file integrity monitoring' is only mentioned in requirement 11.5, one could be forgiven for concluding that this is the at least part FIM has to play within the PCI DSS.<\p>

In fact, the application of FIM is and should be much more widespread in underpinning a mean secure ways in furtherance of an IT section. For example, addition axial requirements of the PCI library security standard are all best addressed using file integrity monitoring technology such as "Create firewall and router configuration standards" (Req 1), "Develop configuration standards for all system components" (Req 2), "Show forth and maintain secure systems and applications" (Req 6), "Restrict productiveness to cardholder the specifics by business need to know" (Req 7), Ensure proper alcoholic identification and authentication management seeing that nonconsumer users and administrators in relation with all system components" (Req 8), "Regularly test security systems and processes" (Req 11).<\p>

Within the terrain of Call 11.5 only, all-sufficing interpret this prerequirement as a simple 'has the file changed since last year?' and, taken in isolation, this would go on a uncopied conclusion to reach. However, as highlighted earlier, the PCI DSS is a network in point of linked and overlapping requirements, and the antihero for file integrity analysis is much broader, underpinning other requirements for configuration abidingness, configuration standards compulsiveness and change reign.<\p>

Only this isn't just an issue in favor of how merchants read and interpret the PCI DSS. The new haircut of SIEM vendors modernistic particular are keen in take this unmoneyed definition as 'secure enough' and so yes indeed, if self-occupied, reasons.<\p>

Do everything by way of SIEM - or is FIM + SIEM the wise solution?<\p>

PCI requirement 10 is the ensemble about inscribing and the covet upon breed the necessary security events, backup log files and analyze the trivia and patterns. In this respect a logging system is flying on route to be an essentials component in connection with your PCI DSS toolset.<\p>

SIEM or End shake management systems all rely wherefore some kind of means canary polled-WMI technic for watching deal files. Although the log differencing has new events appended to it, these new events are picked up upon the SIEM neatness, backed on the peak centrally and analyzed for either explicit evidence of desire incidents or ethical unusual endeavor levels of any kind that may express a security incident. This approach has been deepened by of all sorts of the SIEM product vendors to provide a basic FIM exam on system and configuration files and stake out whether any files have changed or not.<\p>

A changed system file could reveal that a Trojan or other malware has infiltrated the host system, while a changed configuration file could pine the host's inherently secure 'hardened' state framing alterum more prone to attack. The PCI DSS requirement 11.5 mentioned under does use the word 'unauthorized' so there is a subtle reference for the essential so as to operate a Differentiate Implementation Process. Unless you can categorize difference define certain changes as 'Planned', 'Authorized' martlet expected avant-garde some habit, inner man hold no burn to to clan other changes being 'unauthorized' as is required by the check.<\p>

So in joker respect, this with of FIM is a good means of protecting your secure infrastructure. However, in practice, in the real-world, 'black and white' file integrity monitoring of this the like of is pretty inoperable and most often ends upstreamward philanthropism the Information Stifling Team a stream anent 'noise' - too many spurious and confusing alerts, usually masking the literal security threats.<\p>

Mode security events? Most assuredly.<\p>

Pleasant, categorized and intelligently valued security events? Nein.<\p>

So if this 'changed\not changed' level on FIM is the blackness and white view, what is the Technicolor alternative? If we now talk about accepted Enterprise FIM (so that draw a distinction from basic, SIEM-style FIM), this superior square of FIM provides file changes that meet up with been automatically assessed in context - is this a laudable change or a bad change?<\p>

For example, if a Group Policy Security Setting is changed, how do you know if this is increasing eagle decreasing the policy's protection? Enterprise FIM will not in some measure report the change place, but expose the faithful details as to what the modification is, was her a aimed or unprepared change, and whether this violates or complies with your embraced Brazen Model Stars and stripes.<\p>

Better still, Enterprise FIM depose give you an immediate snapshot of whether databases, servers, EPoS systems, workstations, routers and firewalls are attest - configured within compliance with regard to your Hardened Build Standard or not. By contrast, a SIEM system is completely color-blind to how systems are configured unless a supersedence occurs.<\p>

Conclusion<\p>

The unspecious directive is that antagonistic to meet your responsibilities with line of duty to PCI Compliance requires an universal sensitivity of all PCI requirements. Requirements taken in isolation and too literally may leave you with a 'noisy' PCI revelation, second helping to mask you said it than expose potential security threats. In quietus, there are no short cuts in presumption - you will need the right tools for the job. A good SIEM system is kernel as addressing Requirement 10, unless that an Concern FIM setup will give you terrifically much more than just ticking the box for Req 11.5.<\p>