Logicworks, a New York-based cloud-computing provider, announces the launch of Compliant Cloud, the first private cloud service capable of enterprise-level security and compliance. Compliant Cloud is a breakthrough for businesses looking to take advantage of the flexibility and efficiency of cloud-computing without sacrificing the security of traditional in-house IT operations. Logicworks Compliant Cloud provides a full range of solutions including; PCI for e-commerce, SAS-70 and Sarbanes-Oxley required for internal systems at public companies, HIPAA for healthcare applications, Federal Information Security Management Act (FISMA) for government projects and safe harbor for European Union projects hosted in the United States.<\/p>\n","protected":false},"excerpt":{"rendered":"
Logicworks has been a popular choice for demanding infrastructure hosting projects for 17 years, and has a client base that includes Dow Jones, Major League Baseball Advanced Media, NBC Universal, Hearst Corporation, Starwood Hotels, nextEMR, and Wealth Management Systems.<\/p>\n
“We looked at how the internal IT departments of Fortune 500 companies were approaching cloud-computing and decided to offer a similar approach for our enterprise clientele, a fully dedicated VMware environment with managed security features designed to meet the most stringent auditing and compliance standards,” said Logicworks President and COO Kenneth Ziegler.<\/p>\n
Standard features include dedicated VMware ESX cloud processing and storage equipment, separation of confidential data onto independent networks in a demilitarized zone (DMZ), and advanced monitoring services like Intrusion Detection and Prevention Systems (IDS \/ IPS).<\/p>\n
By keeping a razor sharp focus on our sophisticated group of clients and providing them with world-class facilities, support, and expertise, we can in fact surpass the experience of any in-house server infrastructure.”<\/p>\n
http:\/\/www.businesswire.com\/portal\/site\/home\/permalink\/?ndmViewId=news_view&newsId=20100603005236&newsLang=en<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,3],"tags":[],"class_list":["post-1629","post","type-post","status-publish","format-standard","hentry","category-cloud","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1629","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=1629"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1629\/revisions"}],"predecessor-version":[{"id":4116,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1629\/revisions\/4116"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1629"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1629"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1629"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}