Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Each issue (e.g. incident) that comes into support is assigned one of four priorities, each with its own Service Level Agreement (SLA), which dictates our time goal to respond to and resolve the issue, with some definitions in mind:

...

Priority

Incident Type

P1-Urgent

Interruption making a critical functionality inaccessible on a Security Reviewer’s product, causing a severe impact. There is no possible alternative

P2-ImportantHigh

Critical functionality, degraded or unusable on a Security Reviewer’s product, having a severe impact. No acceptable alternative is possible

P3-Normal

Non-critical function or procedure, unusable or hard to use on a Security Reviewer’s product, having a non-critical operational impact. A workaround is available

P4-Low

Procedure unusable, part of a Security Reviewer’s product where a workaround is available or a repair is possible

  • Availability means the schedule of time that Security Reviewer will made staff available to respond to Service Requests or Incidents. All the time are referred to business hours or business days only.

  • Response time is the time elapsed between the Customer is raising a ticket and we first responding to it, assigning the issue. In case of ticketing system is different from ours, Response Time is the time elapsed between the ticket was assigned to us via e-mail and we first responding to it.

  • Update time is defined as the amount of time between when the Customer first creates an incident report using our web ticketing system, providing all information necessary to open the ticket, and when Security Reviewer actually responds and lets the Customer know they’ve Security Reviewer has all the necessary information and has acknowledged the issue, and informs the Client that it is currently working on it. In case of ticketing system is different from ours, Update Time is the amount of time between the ticket was assigned to us via e-mailemail, providing all information necessary to open the ticket, and when Security Reviewer actually responds and lets the Customer know they’ve currently working on it. In order to log and track the resolution of Incidents, Security Reviewer expects that Customer will make every attempt possible to:
    a) Verify that the Incident is reproducible on the Supported Platforms for the related Security Reviewer’s product.
    b) Provide information necessary to help Security Reviewer track, prioritize, reproduce, or investigate the Incidentincident, such as:

    • Customer name and organization.

    • Provide a full description of the issue and expected results.

    • Categorize issues under “Question Type”.

    • List steps to reproduce the issue and relevant data.

    • Provide exact wording of all issue-related error messages.

  • Resolution time is defined as the amount of time between when Security Reviewer first responds an incident report, confirming the issue and when that problem is actually solved resolved. For each Incident reported by Customer in accordance with these procedures, Security Reviewer shall:

    • Confirm receipt of the reported Incident within the Update time as listed

    below
    • in the Priorities section.

    ▪ Set an updated Priority Level for the Incident in accordance with the descriptions below. ▪ Use commercially reasonable efforts to respond to the Incident within the time specified below. ▪
    • Analyze the Incident and, as applicable, verify the existence of the problem(s) resulting in the Incident, which may include requesting that Customer provides additional information, logs, and re-execution of commands to help identify the root cause and dependencies of the reported issue

    . ▪
    • .

    • Set an updated Priority Level for the Incident, if necessary.

    • Use commercially reasonable efforts to respond to the Incident within the time specified.

    • Give Customer direction and assistance in resolving the Incident.

    • Keep a record of ongoing communications with Customer.

    • Use commercially reasonable efforts to resolve the Incident in accordance with the target Resolution times

    • Upon request of Customer, discuss Priority Level and ongoing communication time frame.

We provide 3 different SLA Contracts:

Standard Support Contract

The Standard Support is automatically included with your product license. We always apply:

...

always included to provide help regarding purchased Security Reviewer’s product with a valid commercial license or active subscription. We always apply:

  • Priority: All issue are managed as P4

  • Response: 2 Business Days

  • Update: 5 Business days

  • Resolution: 10 Business days

  • Availability: 8/5 via e-mail mails only (after the ticket was assigned to us )

  • Priority: P4

  • Response Time: 2 Business Days

  • Update Time: Monthly

  • in case of external ticketing system)

with products updates and patching on monthly basis, always accompanied by related technical documentation..

The Service Desk maintains regular business hours of 9 AM to 6 PM CET, Monday through Friday. Tickets and calls emails will be responded to only during these hours.

The default SLA time zone will be CET only.

...

The Gold Support enhance the Standard Support Contract with better Update time and Resolution time, for every purchased Security Reviewer’s product with a valid commercial license or active subscription:

Priority

Response

Update Time

Resolution Time

P1-Urgent

Within 60 (sixty) minutes from remote, after the Ticket opening

Within 4

2 (two) hours

8 (eight) hours

8 (four) hours after the Update Time. Telephone call is .
Direct call available.

P2-ImportantHigh

Within 4 (four) hours from remote, after the Ticket openingWithin 4 (four) hours after the Update Time

8 (eight) hours

8 (eight) hours

P3-Normal

Within 4 (four) hours from remote, after the Ticket openingWithin 24 (twenty-four) hours after the Update Time

2 (two) days

2 (two) days

P4-Low

Within 8 (eight) hours from remote, after the Ticket openingWithin

2 (two) days

5 (five) business days from remote, after Update Time

Availability: The Service Desk maintains regular business hours of 9 AM to 6 PM depending on SLA time zone, Monday through Friday. Tickets and calls will be responded to only during these hours.

...

Platinum Support augments the underlying Standard Support purchased with your product license, by providing named and dedicated support experts that understand your business — helping you to optimize even the most complex hybrid software environments and resolve issues quickly if they arise.

Priority

Response

Update

Time

Resolution

TimeWithin

P1-Urgent

Within 60 (sixty) minutes from remote, after the Ticket opening

1 (one) hour

2 (hours) hours

4 (four) hours

H24 after the Update Time. Telephone call is

.
Direct call available.

P2-

Important

High

Within 2

1 (

two) hours from remote, after the Ticket openingWithin

one) hour

4 (four) hours

8 (eight) hours

after the Update Time

P3-Normal

Within 4 (four) hours from remote, after the Ticket opening

Within

2 (two) hours

8 (eight) hours

8 (eight) hours

after the Update TimeWithin

P4-Low

Within 6 (six) hours from remote, after the Ticket opening

4 (four) hours

8 (eight) hours

2 (two)

business

days

from remote, after the Update Time

In case of multi-national Customer, the default SLA time zones will be maximum 2, declared by the Customer inside the Contract.

Availability: The Service Desk maintains H24 availability, Monday through Friday. Tickets and calls will be responded H24, depending on above priority levels (P1 to P4). Tickets and calls will be responded to only such days.

In case of multi-national Customer, the default SLA time zones will be maximum 2, declared by the Customer inside the Contract.

24/7 Support

An extension of Platinum Support Contract to 24/7 is available and must be purchased separately, with an additional fee.

...

A Release can be Major, Minor or Patch, based on the type of the changes made.introduced:

  • Major Release means a specific edition of the Licensed Product that contains major functionality changes. Indicates a very large change in the core package. Rewrites or major milestones. API changes which are not backwards-compatible. The content and timing of all Major Releases will be determined by Security Reviewer in its sole discretion.

  • Minor Release means a specific edition of the Licensed Product that introduce new features or significant changes in functionality, in a backwards-compatible manner. The content and timing of all Minor Releases will be determined by Security Reviewer in its sole discretion.

  • Patch means bug fixes, security releases, error correction or change in operating procedures whereby the Licensed Product is made functional so that Customer can continue to use it. Security Reviewer may provide Patching or workarounds for a release to resolve a Service Issue for up to twelve (12) months after the earlier of the date the subsequent Release is first made commercially available, and the date the current Release is no longer made available as a commercial offering by Security Reviewer. After such twelve (12) month period, Security Reviewer is not obligated to provide Patching but will support Customer’s update of the Licensed Product to the latest Release. Where Patching are to be delivered to resolve a Service Issue, Security Reviewer will provide Customer with a single copy of a Workaround on suitable media or shall make available the applicable Workaround for download by Customer from Security Reviewer’ website.

Versioning

Our release numbering convention follows the guidelines of Semantic Versioning. Given a version number Major.Minor.Patch and an optional Suffix (e.g. 1.3.0-rc.1):

...