Portfolio

Umbraco development

Building an efficient CMS for UK banking

1: High maintenance and poor security

 

Our client, a UK-based bank, found that users did not have a flawless experience when signing up for a personal deposit account (PDA) online. There was unacceptable risk in the way the website processed sensitive details, and the client relied on IT to make website changes.

2: Custom Umbraco development

 

Our team proposed a like-for-like migration of the client’s website to Umbraco CMS. The first phase provided new environments within Azure, followed by implementation of a platform with enhanced security.

 

The website content was then successfully migrated to the new Umbraco site. Our team launched full managed services to ensure functionality and security. Finally, our team solved the client’s UX issues with development that pushed data directly to their on-premise database.

3: Enhanced experience and security

 

The client received a secure, compliant, high-functioning, and easily adaptable CMS. The Umbraco website kept customer data protected on the client’s database while also integrating with the systems for online PDA sign-ups.

 

Our managed services kept site performance, capacity, upgrades, and back-up in line with best practices, ensuring long-term value.

 

Are insecure systems putting your business at risk?

Our development team will provide a solution.

Info

15th May 2020
Umbraco, cms, development, financial services

Privacy Preference Center

Necessary

Advertising

Analytics

Analytics cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customise our Websites for you.

Google Analytics
The cookie _gcl_au is used by Google Analytics to understand user interaction with the website.

For example, in order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.

The analytics.js library accomplishes this via the Client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.

By default, analytics.js uses a single, first-party cookie named _ga to store the Client ID, but the cookie's name, domain, and expiration time can all be customized. Other cookies created by analytics.js include _gid, AMP_TOKEN and _gac_. These cookies store other randomly generated ids and campaign information about the user.

Google Analytics
_gcl_au, _gid, _ga, gtm_preview

Other

WordPress uses cookies for authentication. That means that in order to log in to our WordPress site, you must have cookies enabled in your browser.

There are two types of cookies set by WordPress.
1 — Session cookies — These are ‘strictly necessary’ cookies as WordPress will not be able to function without it.
2 — Comment cookies — These are not ‘strictly necessary’ cookies and are set when users leave a comment on a post.

Wordpress Session cookies:
Users are those people who have registered an account with the WordPress site.
wordpress_[hash]
wordpress_logged_in_[hash]
wordpress_test_cookie
wp-settings-{time}-[UID]

Wordpress comments:
Comments are usually turned off by default.
If by chance they are still active on a post, asides being turned off when spotted, data from these are not saved by Influential.
- When visitors comment on a post, they too get cookies stored on their computer. This is purely a convenience so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:
comment_author_{HASH}
comment_author_email_{HASH}
comment_author_url_{HASH}

Wordpress, Intercom
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]
intercom-id-[app_id],intercom-session-[add-id]