348
edits
Changes
no edit summary
= Overview =[[File:stacks_001.png|right|300px]]The bxp software (bxp) infrastructure is a multi-tier design to delivery high availability with our own private infrastructure within Amazon Web Services. [[Bxp_software_in_AWS_Cloud_Services]]
=Secure Design=
AWS performs initial environmental and geographic assessments. Data center locations are carefully selected to mitigate environmental risks, such as flooding, extreme weather, and seismic activity. AWS Availability Zones are built to be independent and physically separated from one another.
=Redundancy=
Data centers are designed to anticipate and tolerate failure while maintaining service levels. In case of failure, automated processes move traffic away from the affected area. Core applications are deployed to an N+1 standard, so that in the event of a data center failure, there is sufficient capacity to enable traffic to be load-balanced to the remaining sites
[[File:BER8SER2Infrastructure.png|800px]]
== Firewall Security == The high available firewalls are implemented using Cisco 5510sAWS' network firewalls. This is a managed service with AWS. The Network Firewall includes features that provide protections from common network threats. AWS Network Firewall’s stateful firewall can incorporate context from traffic flows, like tracking connections and protocol identification, to enforce policies such as preventing bxp's metwork from accessing domains using an unauthorized protocol. httpAWS Network Firewall’s intrusion prevention system (IPS) provides active traffic flow inspection so bxp can identify and block vulnerability exploits using signature-based detection. AWS Network Firewall also offers web filtering that can stop traffic to known bad URLs and monitor fully qualified domain names. For more information visit (https://wwwaws.ciscoamazon.com/c/ennetwork-firewall/us/products/collateral/security/asa?whats-5500new-seriescards.sort-nextby=item.additionalFields.postDateTime&whats-generationnew-firewalls/product_data_sheet0900aecd802930c5cards.html == Load Balancing == The load balancers are implemented using CentOS on a virtualised basis. == Web == The web servers are implemented using Windows Server 2008 R2 x64 on a virtualised basis. == Database =sort-order=desc)
= Logical Infrastructure =Load Balancing==The load balancers are implemented using highly available AWS Application/Network Load balancers. This service allows us to protect our encrypted HTTPS connections ensuring the usage of strong TLS1.2 and cipher suite technology. For more information (https://aws.amazon.com/elasticloadbalancing/)
==Server Monitoring==
Live 24/7 monitoring from our AWS support team, with alerts and calls to bxp team if required.
An ISMS for our servers is monitored by Datadog HQ (https://www.datadoghq.com/product/)
==Database==
The web servers are implemented using Windows Server on a virtualised basis.
=Logical Infrastructure=
==Data Segregation==
Within this common infrastructure data segregation is key. Though the solution uses a common infrastructure, logically the data is completely segregated. This segregation occurs at a web and database level.
This area is often referred to as multi-tenancy or multitenancy. Multi-tenancy is an architecture in which a single instance of a software application serves multiple customers. Each customer is called a tenant. In the case of bxp, the software does share common functionality, but each system is a separate instance, as is each separate database. [https://en.wikipedia.org/wiki/Multitenancy Wikipedia - Multitenancy]
A set group of unique identifiers hard coded at the web layer ensures that database connections are only possible to one client database at a time. This is encoded into all operational pages of the solution.
==Database segregation==Each client has their own separate database. Each database begins with a common suite of tables making up the database structure independent of all other databases. As content is added each database grows according to the specific client needs.
Each database is combined with the web segregation to provide full and unique audit trails for all interactions with that database. This is part of the design of the bxp solution.
Strong security and operational procedure controls ensure this segregation is maintained by all personnel with access. All interactions are auditable.
==Server Patching Process==
Servers are checked for patches and updates daily. These updates are downloaded and installed on Thursday evenings as part of bxp' scheduled maintenance hours 22:30-00:30. The exception is made for zero-day updates which are conducted asap.