“);
});
try {
$(“div.lazyload_blox_ad”).lazyLoadAd({
threshold : 0, // You can set threshold on how close to the edge ad should come before it is loaded. Default is 0 (when it is visible).
forceLoad : false, // Ad is loaded even if not visible. Default is false.
onLoad : false, // Callback function on call ad loading
onComplete : false, // Callback function when load is loaded
timeout : 1500, // Timeout ad load
debug : false, // For debug use : draw colors border depends on load status
xray : false // For debug use : display a complete page view with ad placements
}) ;
}
catch (exception){
console.log(“error loading lazyload_ad ” + exception);
}
});

A survey of 300 IT professionals by Fugue, a cloud infrastructure security provider, reveals that most enterprises are vulnerable to security events caused by cloud misconfiguration, including data breaches and system downtime events.

From the report:

  • Nine in ten have real concerns about security risks due to misconfiguration, and less than a third continuously monitor for them.
  • Teams report a frequency of 50 or more misconfigurations each day, yet half of the teams only review alerts and remediate issues on a daily—or longer—timeframe, leading to dangerously long infrastructure vulnerability periods.

Of course, this report (like any vendor-sponsored report) is self-serving. But the message reflects something that I’m seeing a lot today in the real world—and it’s scaring the hell out of me.

Misconfiguration means that the public cloud server instances, such as storage and compute, are configured in such a way that they are vulnerable to breaches. For example, the National Security Agency recently had an embarrassing moment when someone was able to access secure documents from its Amazon S3 instance with just a browser. It was a classic example of misconfiguration, defeating the default configurations that are secure be default.