Despite 95 percent of CIOs expecting cyberthreats to increase over the next three years, only 65 percent of their organizations currently have a cybersecurity expert, according to a survey from Gartner. The survey also reveals that skills challenges continue to plague organizations that undergo digitalization, with digital security staffing shortages considered a top inhibitor to innovation ...
Please observe the following editorial guidelines when submitting blogs to DEVOPSdigest:
DEVOPSdigest recommends that you send an abstract or outline of your potential blog submission to Pete Goldin, Editor and Publisher of DEVOPSdigest, before you start writing the blog, to ensure it is something we would publish.
The following guidelines apply to non-vendors — such as analysts, consultants, integrators and users — who would like to post a blog on DEVOPSdigest. Non-vendor blogs are posted in the BIZDEVOPS Blog.
Blogs from DEVOPSdigest sponsors are also posted in the Vendor Forum, but sponsors gain certain benefits when blogging. If you work for or represent a sponsor of DEVOPSdigest, click here for the Sponsor Blog Guidelines.
If you are a PR or Communications Manager or Agency, click here for some tips on how to interact with DEVOPSdigest.
If you are submitting a quote for a DEVOPSdigest list, such as our annual DevOps Predictions list, click here for guidelines on APMdigest.
All blogs submitted to DEVOPSdigest must be original content that has not been published somewhere else. DEVOPSdigest periodically may request to re-post a blog, if the content is particularly valuable to our readers, but please do not pitch DEVOPSdigest to re-post your blog.
Standard word count for a blog is 500-1000 words. This is not a strict rule. Word counts can be longer if the topic warrants more content. If your blog is longer than 1000 words, however, you may want to consider breaking it into multiple parts. Editorial decisions relating to word count are made on a case-by-case basis.
DEVOPSdigest does not follow an editorial calendar, and usually does not assign a deadline. We post content as we receive it.
DEVOPSdigest posts 1-3 items of primary content — blog or feature — per week. Consequently, there is often a queue of content waiting to be posted.
DEVOPSdigest content is featured in APMdigest e-mails, which go out twice per month, and the current mailing includes content posted since the last mailing.
DEVOPSdigest accepts blogs on topics relating to DevOps including:
■ Development Processes
■ Development Technology
■ Development Automation
■ Agile Development
■ Continuous Development
■ API (Application Program Interface)
■ Development Monitoring and Analytics
■ Application Performance and Quality Testing
If you are unsure whether your topic fits DEVOPSdigest, run your idea by Pete Goldin.
Blogs should be objective, vendor-neutral, thought leadership pieces. Topics should be general industry interest to educate and enlighten our readers. Please do not promote your company, products, partners or any vendor — or criticize the competition — in the blog copy or in related graphics submitted with the blog.
Author and Company Profile
If this is your first blog for DEVOPSdigest, send a one paragraph bio of the author and one paragraph profile of the company, along with the blog.
On The BIZDEVOPS Blog, non-vendor bloggers are welcome to include links at the end of the blog to link to their home page, or other relevant information such as research or events.
Do not place any hyperlinks in the body copy of the blog linking to your company's web pages or any other promotional pages. Hyperlinks in the body copy should only be to support factual points you are making.
All blogs will be reviewed by DEVOPSdigest prior to publication. DEVOPSdigest reserves the right to edit any content submitted, and the publication of any blog is at the sole discretion of DEVOPSdigest. Related links included with the blog are also subject to DEVOPSdigest approval.
If you contribute to DEVOPSdigest, you are free to re-post your own blog on your own website, as long as you mention that the blog was posted on DEVOPSdigest, and include a link to our site.
However, we recommend linking to the blog on DEVOPSdigest.com rather than posting the full blog on your site, to highlight the fact that the content was published by an independent third party. Publication of your blog on a respected industry site provides strong thought leadership credibility for the author and company.
In my first blog in this series, I highlighted some of the main challenges teams face with trying to scale mainframe DevOps. To get past these hurdles, the key is to develop an incremental approach that enables teams to capture value along each step of the journey ...
The key to mainframe DevOps success is in quickly identifying and removing major bottlenecks in the application delivery lifecycle. Major challenges include collaboration between mainframe and distributed teams, lack of visibility into the impact of software changes, and limited resource flexibility with scaling out necessary testing initiatives. Now let's take a closer look at some of these key challenges and how IT departments can address them ...
How much are organizations investing in the shift to cloud native, how much is it getting them? ...
In the shift to cloud native, many organizations have adopted a configuration-as-code approach. This helps drive up application deployment velocity by letting developers and DevOps teams reconfigure their deployments as their needs arise. Other organizations, particularly the more regulated ones, still have security people owning these tools, but that creates increased pressure on the security organization to keep up. How much are organizations investing in this process, and how much is it getting them? ...
More than a third of companies that use serverless functions are not employing any application security best practices and are not using any tools or standard security methodologies to secure them, according to the State of Serverless Security survey, conducted by PureSec ...
The popularity of social media platforms and applications is spurring enterprises to adopt "social business" models to better engage with employees and customers and improve collaboration, according to a new study published by ISG ...
The previous chapter in this WhiteHat Security series discussed Codebase as the first step of the Twelve-Factor App and defined a security best practice approach for ensuring a secure source control system. Considering the importance of applying security in a modern DevOps world, this next chapter examines the security component of step two of the Twelve-Factor methodology. Here follows some actionable advice from the WhiteHat Security Addendum Checklist, which developers and ops engineers can follow during the SaaS build and operations stages ...
The larger the company size, the higher the proportion of low IT performers, according to the State of DevOps: Market Segmentation Report from Puppet, based on the 2017 State of DevOps Survey data ...