Cloudops (cloud operations) and secops (security operations) are quickly evolving practices. While I’m seeing some errors, what’s more common is that ops teams are leaving important things out. If these missing aspects are not addressed, secops will become problematic quickly.
Here are two secops omissions that you can deal with today, even though your public cloud provider won’t tell you about, won’t be on any certification, and is typically widely misunderstood.
[ IDG Research: The state of the cloud: How enterprise adoption is taking shape. | Keep up with the latest developments in cloud computing with InfoWorld’s Cloud Computing newsletter. ]
Link secops monitoring to govops monitoring
Both secops and govops (governance operations) need to be proactive, meaning that they need to adjust based on changing threats in the case of secops, and changing policies in the case of govops.
To read this article in full, please click here