{"id":654,"date":"2005-04-18T00:00:00","date_gmt":"2005-04-18T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/04\/18\/ibm-stresses-app-security\/"},"modified":"2021-12-30T11:37:53","modified_gmt":"2021-12-30T11:37:53","slug":"ibm-stresses-app-security","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/04\/18\/ibm-stresses-app-security\/","title":{"rendered":"IBM Stresses App Security"},"content":{"rendered":"<p>IBM is planning to bolster its development tool set with features to help developers bake security into their applications.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Anthony Nadalin, chief security architect for IBM&#8217;s Software Group, said IBM is looking to do more to address the issue of security throughout the application life cycle, starting during the requirements process and going straight through to modeling and deployment.  &#8220;There is a lot of interest in companies building secure applications and how to guarantee that, so we&#8217;re looking at the notion of security in the application life cycle.&#8221;<\/p>\n<p>Nadalin said IBM is considering enhancing its modeling capability to enable users to integrate security into the process.<\/p>\n<p>The authentication becomes a policy issue, and &#8220;you wind up with a policy-driven model.  It is nearly impossible to retrofit,&#8221; Murphy said.<\/p>\n<p>http:\/\/www.eweek.com\/article2\/0,1759,1787115,00.asp?kc=EWRSS03119TX1K0000594<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-654","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/654","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=654"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/654\/revisions"}],"predecessor-version":[{"id":3141,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/654\/revisions\/3141"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=654"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=654"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=654"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}