Skip to main content

FIM QQ

How many systems will need to be monitored with FIM?
Which type of architecture will need to be deployed?
Which Operating Systems will require monitoring?
Does your environment leverage central configuration management?

How will FIM alerts be evaluated?
Does FIM logs to be sent to a centralized log repository?

Who will monitor and approve changes for FIM? 

What reports should be developed and who should receive these? 

Is FIM required to meet regulatory or standards requirements?

How will FIM be tuned and who will be responsible for identifying new FIM signatures?
Will a SIEM solution be utilized within the environment?


Do you have any PCI DSS requirements? Do you process, store, or forward credit card information?

Do you have a compliance need to test and verify the security of your systems? How do you know if the security measures in place are working? Can you verify that you will know if file or object-level changes occur accurately on servers?
Do you have a regulatory mandate to maintain an audit trail of who made changes to servers and what changes were made?

Do you have a manual or homegrown change reporting process today? Do you know the overhead of managing this type of isolated system?  

Comments

Popular posts from this blog

ESS

ESS is uniquely qualified to help you secure a new era of computing with: ·          Intelligence  – Enterprise security portfolio, with our expert field professionals, are unmatched in their ability to provide the deep analytics needed to ward off the wide range of threats ·          Integration  – Solutions and services systematically integrate both new and existing security capabilities, giving critical visibility, providing comprehensive controls, and reducing complexity ·          Expertise  – Expertise stems from our hands-on professionals and researchers whose know-how is built into our products and services, provided through real-time client feeds and embedded in our professional engagements