BeyondTrust

Security in Context: The BeyondTrust Blog

Welcome to Security in Context

Bringing you news and commentary on solutions and strategies for protecting critical IT infrastructure in the context of your business.

Governance, Risk, and Compliance- Cogs of Security Clock

Posted October 5, 2011    Peter McCalister

Enterprise security, as I’m sure all of you are aware of, is complex. There are a lot of differentfacets and initiatives, and they all fit together in a very intricate and complicated way. The image of a clock, with all those little gears moving together, is how I picture a healthy security program in any given organization. But to think of security objectives like cogs in a clock begs the question of where is the IT parallel? What cogs are crucial to making the clock tick and which ones aren’t? I submit that the governance, security, and compliance mechanisms are the most significant. With these cogs, you set the pattern for security in your enterprise.

Governance is crucial to the plan of your IT infrastructure. We’ve talked about the role of a CSO or IT manager before- it’s these roles that keep the cogs turning in your IT clock. Governance makes sure that your policies are cohesive and that appropriate management is taking place. Without it, whatever security endeavors you have in place will fail.

Risk is another vital element in your security structure. Monitoring the dangers associated with privileged identities is a huge part of why this cog is so important. The management of identities (i.e. – who has access to what information) is key in preventing insider threat and the misuse of privilege. Risk must be kept at a minimum in order for your security system to continue to operate like clockwork (pun intended).

Compliance, the last of the three major mechanisms in your IT organization, is critical to the prosperity of your security plan. The government has mandated several regulations in the defense of data and the protection of information. Following these mandates, as well as passing required security audits, is what drives compliance within organizations.

Leave a Reply

Additional articles

How To Implement The Australian Signals Directorate’s Top 4 Strategies

Posted October 20, 2014    Morey Haber

The Australian Signals Directorate (ASD), also known as the Defence Signals Directorate, has developed a list of strategies to mitigate targeted cyber intrusions. The recommended strategies were developed through ASD’s extensive experience in operational cyber security, including responding to serious security intrusions and performing vulnerability assessments and penetration testing for Australian government agencies. These recommendations…

Tags:
, , , ,
asp-mvc

Exploiting MS14-059 because sometimes XSS is fun, sometimes…

Posted October 17, 2014    BeyondTrust Research Team

This October, Microsoft has provided a security update for System.Web.Mvc.dll which addresses a ‘Security Feature Bypass’. The vulnerability itself is in ASP.NET MVC technology and given its wide adoption we thought we would take a closer look. Referring to the bulletin we can glean a few useful pieces of information: “A cross-site scripting (XSS) vulnerability exists…

Tags:
4bestpracticesaudits-blog

Four Best Practices for Passing Privileged Account Audits

Posted October 16, 2014    Chris Burd

Like most IT organizations, your team may periodically face the “dreaded” task of being audited. Your process for delegating privileged access to desktops, servers, and infrastructure devices is a massive target for the auditor’s microscope. An audit’s findings can have significant implications on technology and business strategy, so it’s critical to make sure you’re prepared…

Tags:
, , , ,