fbpx

Security

1 INTRODUCTION
Today’s technology leaders are charged with securing and protecting the customer, employee, and intellectual property data of their companies in an environment with increasingly complex security threats. As cloud computing has become more widely accepted, a number of information security concerns have been raised.

In a computing context, security comprises cybersecurity and physical security — both are used by enterprises to protect against unauthorized access to data centers and other computerized systems. Information security, which is designed to maintain the confidentiality, integrity and availability of data, is a subset of cybersecurity.

Ensuring cybersecurity requires the coordination of efforts throughout an information system, which includes:

• Application security
• Information security
• Network security
• Disaster recovery/business continuity planning
• Operational security
• End-user education

In the following section, we will be covering on how AGHRM handles the security for each of these layers.

2 AGHRM SECURITY OVERVIEW
2.1 Server architecture

Below is a high-level representation of AGHRM applications.

There are primarily 2 sets of servers:
a. Web – Customers will be using AGHRM applications via one of the web servers. This set of servers will be running MS IIS as well as AGHRM suite of solutions.

b. Database – Stores AGHRM’s customer data. Runs MS SQL Server.

2.2 Application Security

Below are the key considerations for AGHRM’s application security.

• Authentication – All passwords are encrypted with cryptographic hash function and a secret cryptographic key.

All authentication requests are performed using one way hash to ensure the security of the passwords.

• Authorization and Access Control – AGHRM is a role based system with 3 main roles.
o Employee – User can only view/manage his/her own records.
o Manager – User can only view/approve/reject requests from his/her own team members.
o Administrators – User is able to configure policy as well as manage transactions. Can be restricted by module and companies.

• Session Management – Users are automatically logged out of the system if they have been idle for more than a specific period of time. Typical timeout period is 20 minutes. However, this setting can be changed at a per customer basis.

• Command Injection Flaws – All data input fields are validated by AGHRM for Cross Site Scripting as well as Command injection attacks by default.


2.3 Information Security

Techopedia defines as follow:

“Information security (IS) is designed to protect the confidentiality, integrity and availability of computer system data from those with malicious intentions.”

2.3.1 Confidentiality

Confidentiality refers protecting information from being disclosed to unauthorised parties.

Data Segregation
AGHRM is a multi-tenant Software-as-a-Service (SaaS) application. We provide 2 types of hosting:
a. Shared
For shared hosting, multiple customers are hosted within the same server. Each customer has a separate portal linked to a separate database instance. This approach ensures that each customer’s data are physically stored in separate database and there is no possibility of customers accessing another customer data. Below is a logical view of our data segregation model.

b. Dedicated
For dedicated hosting, only 1 customer will be hosted within 1 server.

2.3.2 Integrity

Integrity – protecting information from being changed by unauthorised parties.

Users access AGHRM via the internet protected by Transport Layer Security (TLS). This secures network traffic from passive eavesdropping, active tampering, or forgery of messages.

2.3.3 Availability
Availability – to the availability of information to authorised parties only when requested.

User can only access AGHRM’s portal upon successful logins.

2.4 Network Security

AGHRM host our servers with global hosting partners like Amazon Web Services and Microsoft Azure.
You can find the data centre certification compliance in the URLs below.
https://d1.awsstatic.com/whitepapers/Security/AWS_Security_Whitepaper.pdf
https://azure.microsoft.com/en-us/overview/trusted-cloud/

Access to the server is tightly controlled.
• For web servers, only HTTP and HTTPS ports are open for public.
• For database servers, only SQL connection is accepted from authorized servers.

2.5 Business Continuity Planning
2.5.1 Objective

The objective for Business Continuity Planning to document down AGHRM’s processes to ensure that our customer are able to operate our systems with minimal disruption to their operations.

Below is AGHRM’s targets for shared cloud customers. If the Customer’s plan is covered by SLA, please refer to the SLA for the stated targets
• Recovery Time Objective (RTO) of 8 hours
• Recovery Point Objective (RPO) of 4 hours

2.5.2 Backup Policies
Below is an overview of AGHRM backup policy.

a. A backup image of the production server is done every 24 hours. These backups are then stored in a separate data centre from the production servers.
b. On a nightly basis, customers’ database are also backed up and stored in a remote location.
2.5.3 Annual Restoration Exercise

AGHRM conducts annual restoration exercise to determine the following:
a. Server Image can be restored
b. Database backups can be restored


2.5.4 Standard Procedure during outage incident

Below is the process flow during outage incident.

2.6 Operational Security

AGHRM provide password policy tools to help organizations enforce their IT security policies.