In the era of increased data security threat from both outside and inside of your enterprise, you need to be proactive in your approach. On the government’s side, it wants to ensure the enterprise IT operations are regulated for the sake of data security of the citizens. In order to achieve this, government or the competent statutory authority issue regulations for the enterprises IT operations to be complied with. By complying the regulation, not only you are fulfilling the statutory requirements, you are also fortifying your enterprises security to the level acceptable to the external world.
Growing List of Compliance Regulations
One important point of concern is the growing number of Compliance Regulations issued by various statutory authorities. Already there are Sarbanes-Oxley Act (SOX), Payment Card Industry (PCI), Health Insurance Portability and Accountability Act (HIPAA), Gramm-Leach-Bliley Act (GLBA). Further more there are California Senate Bill No. 1386, Federal Information Security Management Act (FISMA), and SCADA security best practices. Each regulatory compliance will be outlining its own separate set of reports which needs to be presented to the IT auditors. So how the small and medium enterprises with their limited IT budget will cope up with growing demand of regulatory compliance.
How to address the ensuing scenario
An ideal solution would be to generate customized set of reports for each compliance to be available as pre-built package. But customizing the set of reports will be time consuming and will be involving software developers with development time changes in the software application. This may not be desirable as every time a new regulation is introduced you have to carry out the exercise to comply with. What you can look out for is an application which allows you the flexibility of customization of the available set of reports to make ready for the new compliance. Further, you choose to fine tune or prune the set of reports meant for the existing regulatory compliance. Further more, you may feel that it will be nice to have the reports generated periodically without your intervention manually.
A solution in sight
AdventNet ManageEngine with its fore thought addresses your above stated problems. The EventLog Anayzer 5 allows you create a set of reports for a new compliance. This value added feature removes your burden of customizing the application every time you require reports for a new regulatory compliance. It takes no time and can be created by the System Administrator. Another feature of EventLog Anayzer 5 is to allow customization of the set of reports for the existing compliance report. This is another value addition that ensure that you submit only required reports and remove reports which are not required or add a new one which is required. You dodnot have to panic for minor changes in the regulations. What more, EventLog Anayzer 5 allows you to schdule the compliance report generation automatically at periodic interval. You can sit back and relax. The EventLog Anayzer 5 comes packed with a lot more features. Get the details here.
Want to see it to belive it, try EventLog Anayzer 5. You can download it from here. The full functionality download is available free for thirty days trial.
Help others find this article:
| 
| 
| 
SIM through Compliance
admin July 17, 2006
Author: parthasarathi
Mood: Cool I came across an article in S-OX
| Quote: |
| Compliance is defined as being in accordance with authoritative requirements. That means being up to date on guidelines, processes and practices. These processes and practices are oriented around such requirements as:? Only authorized user/systems can access and modify specific information they require,? The privacy and integrity of the information and systems must be maintained and assured,
? Audit records are maintained and indisputable, and ? Operational best practices are in place and improved. Regulations, today, may differ in substance but tend to create a group of common requirements. These requirements include: ? Event collection and retention, ? Activity review and assessment, ? Data integrity and chain-of-custody, ? Use audit reduction tools, ? Investigation and forensic analysis, and ? Reporting to and by appropriate personnel. Most security event management (SEM) and security information management (SIM) solutions focus on incident response ? consolidating alerts to respond to visible threats and attacks. And, that?s important. But, as will be evident, the back end of the SIM process ? event data analysis and retention used for reporting, audit and investigation ? is usually half-baked. As a result, compliance support is often spotty. |
So as mentioned, Compliance is an important Security Information Management(SIM) solution.
Let us see how EventLogAnalyzer(ELA) fairs against the above compliance requirements.
ELA provides reports which meet
HIPAA(Health Insuraance Portability and Accountability Act),
SOX(Sarbanes-Oxley) and
GLBA(Gramm-Leach-Bliley Act) security standards under Compliance.
Currently ELA provides the following reports under Compliance section which meets the above security standards.
1. Successful User Logons - Identifies all the user logon events
EventIDs supported: (528,540)
2. User Logoffs - Tracks all the user logoff events
EventIDs supported: 538
3. Logon Failures - Tracks all the failed user logon events
EventIDs supported: (529, 530, 531, 532, 533, 534, 535, 536, 537, 539)
4. Audit Policy Changes - Tracks all the changes done in the audit policy
EventIDs supported: 612
5. Audit Logs Cleared - Tracks all the audit logs clearing events
EventIDs supported: 517
6. Object Access - Identifies when a given object (File, Directory, etc.) is accessed, the type of access (e.g. read, write, delete) and whether or not access was successful/failed, and who performed the action
EventIDs supported: (560,562,563,564,565,566,567,568)
7. System Events - Identifies local system processes such as system startup and shutdown and changes to the system time
EventIDs supported: (512,513,514,515,516,518,519,520)
8. User Account Changes - Identifies all the changes done on an user account like user account creation,deletion, password change etc.,
EventIDs supported: (624,625,626,627,628,629,630,642,644)
9. User Group Changes - Identifies all the changes done on an user group such as adding or removing a global or local group, adding or removing members from a global or local group,etc..
EventIDs supported: (631 - 641) and (643 - 646)
10. Successful User Account Validation - Identifies successful user account logon events, which are generated when a domain user account is authenticated on a domain controller
EventIDs supported: (672,680)
11. Failed User Account Validation - Identifies unsuccessful user account logon events, which are generated when a domain user account is authenticated on a domain controller.
EventIDs supported: (675,681)
If you would like to enhance the compliance reports further, do let us know.
Thank You,
Parthasarathi
Help others find this article:
| | |
