MadCap Central leverages the security, power, and flexibility of the cloud to mitigate or eliminate many of the technical hurdles faced by both content creators and information technology professionals. The overhead traditionally associated with managing complex systems can hinder the ability to create content and deliver content efficiently. The goal of this
Security and privacy are top priorities at MadCap Software, especially when providing customers with a cloud-based system in Central. We are committed to keeping your files, data, and communications secure. Therefore, in choosing Microsoft® Azure as a partner, we focused on selecting a security center that understands the importance of privacy and complies with the highest international and industry-specific compliance standards and uptime guarantees. Microsoft Azure regularly undergoes rigorous third-party audits to ensure and verify the highest level of security controls.
For more information, see the following:
The infrastructure for MadCap Central is hosted by Microsoft Azure, leveraging secured data centers worldwide. These Azure data centers are ISO27001 certified. For details, see https://www.microsoft.com/en-us/cloud-platform/global-datacenters.
The primary data center is located in Sacramento, California. A secondary read-only data center is located in Chicago, Illinois. Additional failover web servers located around the world are also available. In the event of a data center outage, MadCap Software engineers can restore your data when needed, with no interaction needed from the customer.
In addition to data stored in the database, the source control provider (Git) has the ability to failover in case of an outage. This is essential in handling mission critical data in the event of a catastrophe.
MadCap Flare projects can be uploaded to Central, thus creating copies of those projects on the cloud. From the cloud versions of your projects, output files can be generated and published. In addition to Flare source and output files, Central hosts many other types of data, including user and team information, task details, communications between individuals, and ancillary file attachments.
When Flare projects are uploaded to a Central license, they are bound by a Git source control connection.
The following objectives are important for this relationship:
- Easy Access Projects are hosted in the cloud, which means they can be accessed from anywhere.
Security Projects are stored securely in the cloud. Communication between your local desktop and the cloud is over SSH (Secure Socket Shell) and HTTPS (HTTP over SSL). This is an encrypted, secure channel of communication. Source control data is secured by username, password, and SSH keys.
- Data Transference Users can synchronize the local and cloud versions of Flare projects after changes are made to files. In addition, you can retrieve files to a local machine whenever necessary. Uploaded projects can be imported and generated output files can be downloaded from Central.
- Storage MadCap Central stores user data in different ways depending on the nature of the data. Some examples of data storage include encrypted SQL databases, source control repositories (GIT), and Azure blob storage.
Sensitive data—such as user credentials and company information in the database tier—are stored using encryption to mitigate unauthorized access to data, and ensure your information is stored securely.
- The methods of storing data follow industry security standards and offer a highly scalable solution to ever expanding storage management tracking needs.
- If you choose to cancel your subscription, hosted data can be wiped at your discretion.
- Backups All data is backed up daily. All user data in Central database backups are encrypted, transmitted remotely, and stored securely. This helps prevent unauthorized access.
Every MadCap Central subscription includes access to our highly scalable cloud-based build server. Because MadCap Central is a cloud-based solution, content creators can rapidly generate and publish their content with minimal effort while benefiting from a high level of security, scalability, and durability, something that would otherwise require skilled IT resources to implement. Published output is hosted on a robust, secure, geographically redundant web application server.
With that in mind, the following are important considerations:
- Reduced Hosting Costs You can host all of your projects within Central and never worry about managing or scaling costly web servers. Whether you have a small, single project or several large projects, you can host and manage all of your content in one place.
- Automation and Convenience From Central, you generate and publish output with minimal effort. You also have the ability to quickly roll back published outputs when necessary, with the click of a button. Builds can be initiated manually or they can be scheduled. All of this can be done from any device supporting the browser-based interface.
- Availability and Monitoring Your content is vital to your company, so 24-hour availability of the web server is crucial, as is constant uptime monitoring. All components of MadCap Central are monitored 24 hours a day, 7 days a week, 365 days a year using remote monitoring systems. MadCap Software has staff on hand to respond to outages and security breaches.
- Security Management Data in MadCap Central is secured in the following ways:
- Web services have built-in load balancers to stave off most DOS (Denial-Of-Service) attacks.
- We provide unauthorized access monitoring and incident response. Any breaches in data security will be reported to affected customers.
- User portal and API endpoints (i.e., the connection between Flare and Central) are secured via user authentication.
- All data endpoints are secured using SSL. The user portal, API endpoints, source control provider (Git), and all backend system communications are all encrypted.
- Published builds that are not set to “Live” are secured by user authentication.
Scalability As your content management needs grow, so will your demands for a system that dynamically scales as well. Over time, the builds that you generate on Central will consume more and more space. Central offers ease with scalability for your output, which helps to eliminate worries about CPU, memory, and disk-intensive projects.
The Service Level Agreement (SLA) for hosted output on MadCap Central is 99.97%. This monthly uptime percentage applies to the total guaranteed availability of your output and the systems (storage and web applications) used to host it. This SLA is guaranteed through Microsoft Azure.
Much of the work in MadCap Central (e.g., management of users, teams, tasks, projects, and builds) requires user interactions to be performed through a browser. In addition to Flare requiring end-to-end encryption, all traffic from your web browser to the MadCap Central portal is also secured using industry standard security practices such as SSL.
Following are some of the notable features in Central that contribute to a secure, accessible work experience:
Permissions In Central, permissions allow you to dictate which users can see certain information and perform a variety of functions. In addition to basic permissions, there are several administrator-level rights that can be set, giving you the most flexibility to control how your data and files are being managed and distributed.
- Importing Projects If another user uploads a Flare project to your MadCap Central license and you do not yet have that project on your computer, you can import it.
You can do this from the MadCap Central window pane in Flare.
- Downloading Builds
Purchasing Seats and Space Built-in widgets inform you when space or user count becomes a concern.
Single-bound and Dual-bound Projects When you upload a Flare project to Central, the files are connected to Central via an integrated source control system. Your interaction with source control can follow one of two models—single-bound or dual-bound. Single-bound projects are not bound to an additional third-party source control provider; they only use Central's source control system. Dual-bound projects, on the other hand, are already bound to another source control provider, and therefore are bound to both the original third-party source control provider and to Central.