Versions Compared

Old Version 2

changes.mady.by.user David Chmielewski

Saved on

compared with

New Version 3

changes.mady.by.user Kristafanie Somers

Saved on

Key

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


Page Properties
hiddentrue


CategoryIntegration and Automation
DescriptionConnects QFD to internal services through an additional layer of security.


Connects QFD to internal services through an additional layer of security.

Benefits of using this Addon

Creates a secure and direct connection to QFD for service calls.

What does it replace?

This replaces using TLS alone as a method of securing transmission.

What phase is this recommended in?

This is recommended in tandem with any core banking integration.  It is not necessary or recommended for user browser-based access scenarios.

How long from phase kickoff can this be implemented?

Upon receiving the necessary shared keys, encryption settings, etc.. this can typically be implemented within a month.

Who is responsible for what to implement this addon?  What information is required to implement this addon?

Quavo Responsibilities
  1. Work with client to understand connection options, methods and IP ranges in use
  2. Upon receiving the necessary shared keys, endpoints, encryption settings, etc.. make the secured connection available to QFD within a month
Client Responsibilities
  1. Work with Quavo to understand available options for secure connection
  2. Provide necessary shared keys, endpoints, encryption settings, etc.. to make the secured connection within two weeks of phase kickoff
  3. Test the connection and provide a point of contact for any issues or maintenance in the future
Third Party Responsibilities

What does a timeline look like for implementing this addon?


Weeks to completion/Responsibility mapping
PartyKickoff123456789101112
Quavo
112222





Client

1

2

1

2

2

3

2

3

2

3

2

3







How is pricing determined?

MetricDescription
Monthly ChargeA flat fee is assessed per month, regardless of the amount of traffic or usage of the tunnel.

What success criteria should be met prior to going live?

Connection should be made between QFD and the client service endpoint through the tunnel.  This should be done in test, and then verified in production after deployment and before letting users into the system.

Any best practices for implementation or things to know after going live?

This can be a little tricky to set up and ensure routing is available end