IT Security Requirements for a new IT System

IT Security Requirements for a new IT System

Ownership and Criticality of the System:

Business Owner (Name, Department and Designation);

IT System Manager (Name, Department and Designation);

Project Manager;

Project Name;

Cost Charge Code;

Confidentiality, Integrity and Availability rating of the System (Define Worst Case Impact if each of the components is affected).

Availability rating should determine the RTO and RPO of the system.

Describe the scope of change introduced by the project.

Describe the purpose of the system and its functions.

Describe the user base of the system.

Provide inter-system (between different systems) connectivity diagram.

Provide intra-system (within the system) connectivity diagram.

Indicate the Datacenter (DC) where each system is hosted.

Data-In-Motion Encryption – All data transfer from component to component should be using secure protocols which provides encryption of the data being transferred (SFTP, FTPS, Secure-JDBC, SSL, SSH, etc)

Data-At-Rest Encryption:

Option 1 – Application Server level encryption of data before storing into Database (Application administrators have full access to data)

Option 2 – Database level encryption of data (Application administrators and DBAs have full access to data).

Option 3 – Disk/SAN level encryption of data (Application administrators, DBAs and OS administrators have full access to data).

Password Controls:

Password should enforce the inclusion of Uppercase, Lowercase, Number and Symbol.  Enforce the non-usage of past 10 passwords.  Enforce password expiry for every 90 days.  Passwords must use a minimum of 15 characters.

[Guidance: Use Passphrases instead of a word.  Example: IHave1cat&ILoveIt! ]

Two-Factor Authentication should be used for access to application/systems over the Internet.  The second factor being SMS OTP or Hardware Token OTP.

Transaction Signing (OTP generated from Hardware Token based on input value related to the transaction or input value sent through SMS) should be used for authorizing financial transactions and for changing of critical customer data, over the internet.

Session Inactivity:

(i) [Optional] The session should be locked after a pre-defined period of inactivity;

(ii) The session should be logged-out after a pre-defined period of inactivity;

Confidential data at Endpoint Devices:

Confidential data should not be stored into disk storage in Endpoint devices, without a strong Need-To-Have.  If there is a strong Need-To-Have, the data should be stored into Encrypted Containers and the Integrity of the Container should be verified before the data is re-used by the application.

Cache at Endpoint Devices:

Cache used in endpoint devices should be cleared when the application logs out.

Critical Processes at Trusted System:

Input Validation, Output Encoding, Authentication, Authorization, Session Identifier Creation, Cryptographic Functions to protect secrets from Application User and Logging Controls should be implemented at the Trusted System – at the Server side; and not at the User Endpoint.

Authentication should be required for accessing each page and resource at the server side, unless public usage is intended. 

Access Control:

Please provide Access Roles-Permissions Matrix (including Business and IT).  Please indicate which Roles are classified as Privileged Roles.

Security Logging:

Process for recording, protection, retention, ~review of security logs (login/logout, change to access rights, security configurations, etc) should be established.

Activity Logging:

Process for recording, protection, retention and ~review of activity logs should be established.

Secure Coding Practices:

Use OWASP Secure Coding Practice Quick Reference Checklist during code development and review.

Integrity of Golden Source Data:

Any data that is received by the application to be used as a golden source should be integrity verified by the Business Owner.

Network and Application Penetration Testing:

Internal Network and Application Gray Box Penetration Testing should be performed for Internet Facing Systems and Critical Internal Systems before Go-Live.

Platform Vulnerability Assessment:

Platform (OS, DB, and Device) vulnerability assessment should be performed before System Go-Live.

Anti-Malware Protection:

Anti-Malware Solutions should be installed on all Wintel Platforms supporting the System.

Support Documentations:

Documentations should be created to ensure that there is adequate information to support ongoing operations, problem resolution and future maintenance of the system.

Project Level IT Security Requirements (Non-Functional Requirements) – https://github.com/GreenDiary/risk_assessment_best_practices/blob/master/IT_Security_Requirements_Project_Level_v0.01.docx

IT Security Requirements for a new IT System

Leave a Reply

Your email address will not be published. Required fields are marked *