Incident response and management for Pega Cloud Services

This content applies only to Cloud environments.

This article is part of the Pega Cloud Services Subscription Documentation.

Pegasystems works to resolve incidents that affect the Pega Cloud Services network and client environments.  Pegasystems is committed to client satisfaction by being proactive and working to continually improve the following areas:

  • Preventive safeguards in Pega Cloud Services environments
  • Reduction of incident occurrences
  • Incident response and resolution

Pega Cloud Services incident response and management includes:

  • A help desk that responds to client support request calls 24 hours a day, seven days a week.
  • A web-based, mobile-enabled support request ticketing system that is used by clients and the Pega Cloud Services support teams for managing, tracking, monitoring, and communicating incident status from submission through resolution.
  • Security monitoring capabilities which are specifically designed to concentrate on security issues.  Pegasystems' security and networking engineers proactively develop and implement industry-standard security practices for identity access management, data storage, and compliance to help verify the implementation of the agreed security controls for the client's Pega Cloud Services environments.
  • Client support facilities replicated across the globe, which provide environment monitoring (network, database, cloud instances, etc.) and incident response resiliency, with managed shift handovers and on-call scheduling for coverage 24 hours a day, seven days a week.
  • Three tiers of technical and engineering staff to provide incident response, triage, root cause analysis, and to work toward resolution. Response procedures include the use of standard operating procedures that are maintained and kept current in a knowledge base, escalation to higher-expertise tiers and supporting teams, and bridge calls for collaboration.
  • Incident severity, impact, and type classification for prioritization of tickets and assignment of appropriate personnel, with supervised monitoring of ticket status and progress.
  • Contingency and disaster recovery plan activation and escalation, in the event of a major incident that involves multiple clients.
  • Partner and vendor incident response support (for example, for Amazon Web Services) as needed for triage and resolution.
  • Reporting and analysis of incident response performance metrics to work to achieve SLAs.
Did you find this content helpful?

66% found this useful