Monthly Archives: March, 2017

Can You Measure Your Building’s Penetration Risk?

March 23rd, 2017 Posted by Security & Surveillance 0 thoughts on “Can You Measure Your Building’s Penetration Risk?”

“Detailed follow up to the first article on the measurability of your building’s penetration risk. A combination of good basic insight and strategy.”

– Todd Hepler, Digitek Security


The following article written by: Security Magazine

In Part I of this series, we emphasized how enterprises cannot adequately manage their risk of physical penetration without knowing exactly who comes and goes from their facilities. We presented the argument that as ESRM becomes a fundamental discipline in managing enterprise security, we all must stop running from the “elephant in the room” by implementing a real, effective tailgating prevention strategy. Combined with other analytical methods available today, this will allow security professionals to more effectively meet the challenges of our increasingly insecure world. In Part II, we’ll explain how to achieve measurable, predictive data to prove the value of the work you do.

Click Here To Read More

Read Part I

Learn More about Digitek Security.

Can You Measure Your Building’s Penetration Risk?

March 21st, 2017 Posted by Security & Surveillance 0 thoughts on “Can You Measure Your Building’s Penetration Risk?”

“New Tech Helping Security Managers Know Who Comes And Goes.”

– Todd Hepler, Digitek Security


The following article written by: Security Magazine

Interesting read about the challenges security professionals face related to penetration risk measurement; In the follow up article learn how a tailgating prevention strategy actually works and the metrics that can help predict your risk of penetration.

The irony is that given today’s emphasis on security, security professionals are asked to provide a return on investment, mitigate workplace violence, and plan for multiple emergency responses, all while being under-resourced.

If security managers cannot adequately answer who exactly comes and goes from their facilities, how can they say they are protecting their company’s brand, assets, IP, and employees? What other executives with multi-million dollar capital and operational budgets are considered successful managers, yet cannot measure spending decision outcomes and prove an ROI? Since when does a “Perceived improvement” constitute a good investment? How do you communicate that you are reducing risk if you don’t have a baseline from which to measure the reduction?

Click Here To Read More

Follow Up Article

Learn More about Digitek Security.

Analysis: Rethinking cloud architecture after the outage of Amazon Web Services

March 13th, 2017 Posted by Technology 0 thoughts on “Analysis: Rethinking cloud architecture after the outage of Amazon Web Services”

“A thoughtful, thorough recap of the recent AWS outage and a look at the key difference between durability and availability when it comes to cloud architecture.”

– Patrick Torney – eDot


The following article written by: Geek Wire

BY BRIAN GUY on March 5, 2017

Thanks to innovation from companies such as Amazon with AWS, Microsoft with Azure, and Google with Google Cloud Platform (GCP), organizations of all sizes are today increasingly more agile and competitive. Cloud provider partners like Dev9 enable organizations to optimize their journey to the Cloud.

But on Tuesday, February 28, 2017, many people found that their smart phone applications were no longer working properly, many web sites were down and the Internet in general just seemed broken. This is what happens when AWS, the largest Cloud provider, experiences a “service disruption.”

What makes this past week’s outage unique is that unlike prior outages, “service disruptions” or “service events” as Amazon calls them, this week’s web site outages and mobile application failures were not the result of organizations not following Amazon’s best practices, otherwise known as the “Well-Architected Framework.”

In prior AWS outages, such as the 2016 “Service Event in the Sydney Region” where an entire Availability Zone (AZ) failed, organizations that followed Amazon’s Well-Architected best practices were not negatively impacted. This 2017 outage will no doubt cause Amazon to reassess its Well-Architected Framework and introduce new best practices focused on S3 availability.

Indeed, even the AWS Service Health Dashboard (SHD) itself was impacted due to its dependency on S3 in a single region. Amazon has now re-architected its dashboard to be multi-region.

Full Story

Learn More about eDot.

Archives