Resource search results
1 - 10 of 595
I need to post the updated version of the datasheet to these URLs > https://azure.microsoft.com/en-us/support/plans/developer/ > https://azure.microsoft.com/en-us/support/plans/standard/ > https://azure.microsoft.com/en-us/support/plans/prodirect/
This document is intended for Azure customers who are considering deploying applications subject to SOX compliance obligations. It provides customer guidance based on existing Azure audit reports, as well as lessons learned from migrating internal Microsoft SOX relevant applications to Azure.
This document explains the following aspects of Azure Active Directory: • Azure AD Components: What are the different components of Azure AD. This will help you to understand the later sections of the document. • Core Data and Location: What customer data is used by Azure AD and where is it located. • Data Protection: How is the directory data protected at transit and at rest. • Data Flow: How data from various sources such as on premises directories and applications flows to and from Azure AD. • Data and Operations: What data and operational procedures are used by the Azure AD engineering team to manage the service. The target audience of this document is enterprise security evaluators, identity, and access management (IAM) architects, policy makers and regulators, as well as customers with compliance requirements or regulated environments.
Deploying Microsoft Azure solutions can give educational organizations a method of focusing on their core business—education—while maintaining cost-effective IT services in a more secure FERPA-compliant environment. However, it is important for educational organizations to understand their unique threat environment so that they can see what they need to deploy onsite and how it meshes with what Microsoft Azure provides in the cloud. Using the shared responsibility strategy, Microsoft can help assure the protection of student data and FERPA compliance. This paper will be most helpful to those in educational organizations who need guidance and best practices in designing secure solutions on Azure.
The goal of this GxP guidelines document is to provide life sciences organizations with a comprehensive toolset for using Microsoft Azure while adhering to industry best practices and applicable regulations. It identifies the shared responsibilities between Microsoft and its life sciences customers for meeting regulatory requirements, such as FDA 21 CFR Part 11 Electronic Records, Electronic Signatures (21 CFR Part 11), and EudraLex Volume 4 – Annex 11 Computerised Systems (Annex 11).
Microsoft Azure - Response to NZ GCIO Cloud Computing Information Security & Privacy ConsiderationsIn 2014 the NZ Government Chief Information Officer published a due diligence framework for agencies to use in evaluating cloud computing services
This document is meant to provide customers who must address and comply with the SEC’s Regulation Systems Compliance and Integrity (SCI) with an overview of the Microsoft Azure features and services available to them to help enable their success and compliance. The U.S. SEC adopted Regulation SCI and Form SCI in November 2014 to strengthen the technology infrastructure of the U.S. securities markets. The Regulation SCI is designed to reduce the frequency of system incidents, improve resiliency when incidents do occur, and increase the SEC's oversight and enforcement of securities market technology infrastructure.
This paper addresses common security and isolation concerns pertinent to the electric power industry. It also discusses compliance considerations for data and workloads deployed to Azure or Azure Government that are subject to the North American Electric Reliability Corporation (NERC) Critical Infrastructure Protection (CIP) standards.
This e-book is designed for growing technology companies wanting to understand and calculate the challenges, opportunities, and tradeoffs faced in building and scaling their software business. This guide covers: • How Azure’s capabilities and built-in services help level the playing field with enterprise competitors • How both business and technical processes can be more efficient and affordable with Azure services • Specific savings you could realize by leveraging the Azure Pricing Calculator to better predict costs
Many corporations and public agencies are looking for an easy path from their existing mainframe applications to the cloud. Mainframe online transaction processing (OLTP) systems still work, which is why they remain in use across the Fortune 500. But today’s organizations want the benefits of cloud computing. This guide by Larry Mead and Azure Global Engineering shows how the path to the cloud often starts with a mainframe's transaction processing (TP) monitor. This guide tells you how to use TP monitor emulation software on Azure to run even the most complex CICS applications in the cloud. The emulation environment creates all the interfaces that the application expects to see, so it can run unchanged from within a virtual machine (VM) on Azure. Several vendors offer TP monitoring emulators that meet different requirements. This guide can help you ask the right questions.