Log Integration Patterns
Save over 10 hours a week as every project needs to integrate with your SIEM
I’m the co-founder of Identity Revive. We can help you:
Help you with all your cyber security logging and monitoring needs.
Architect, design, deliver and run your cyber security controls in code so you are compliant with regulation and don't suffer from a cyber incident.
Make sure you are getting value out of your Managed Service Providers (MSP’s) and help them use less ClickOps so you get charged less and they make fewer errors.
Also remember if you are a Not-For-Profit (NFP) or in Education or Health sectors as an Non-Government-Organization (NGO), we provide free consulting as a way to Give Back to the community and our Country (Australia). Email me at: rakkhi@identityrevive.com .
Background / Description
Back in the 1970’s they came up with AAA (Authentication, Authorization, Auditing). That is the basics for security. Protect the front door (identity), know what happened (logging). These days you can drive a lot of correlation and automated actions, including using AI and Machine learning from logs.
If you have ever been through an incident, knowing what happened is crucial.
If all that doesn’t convince you, well most regulation and industry frameworks such as NIST or PCI-DSS will require you to log and monitor.
Log integration patterns
In addition to identity and access, the one thing all your projects will need is:
What to log.
What to configure for each log.
How to integrate with your SIEM or whatever system or service you use to provide cyber security monitoring.
If you are an organization with approx 3000 staff, 2 geographies, 20 major projects on the go at any one stage, 5 security architects, these patterns will save you about 10 hours per week. More savings the bigger you are and the more you can get projects and solution architects and designers to self service while maintaining within risk appetite.
