National Information Security Policy and Guidelines | Ministry of Home Affairs
limiting the session lifetime, applying appropriate logout function and idle
session timeout, and filtering invalid sessions
b. Ensure that sessions established by applications are secured by using
appropriate encryption technologies, especially when sensitive information
is transferred using HTTPS/TLS protocols
c. Ensuring encrypting sensitive session contents using protocols such as
S/MIME
15.5.7.
Input validation: Ensure applications validate input properly and restrictively,
allowing only those types of input that are known to be correct. Examples
include, but are not limited to, cross-site scripting, buffer overflow errors, and
injection flaws amongst others
IG 70
a. Organization should ensure that applications validate the data on the
server-side and not on client-side
15.5.8.
Error handling: Ensure applications execute proper error handling so that errors
will not provide detailed system information, deny service, impair security
mechanisms, or crash the system
IG 71
a. Ensure that the application will provide meaningful error message that is
helpful to the user or the support staff
b. Ensure that errors are detected, reported, and handled properly
c. Error messages shouldn’t reveal much information
d. No debug message for errors, no debugging in application itself
e. Application safe mode for occurrence of unexpected instance
15.5.9.
Application security testing: Ensure comprehensive security testing of
applications in its lifecycle. The testing may be performed either in-house or in
government approved labs :
IG 72
a. Applications should be subjected to rigorous application security testing and
risk assessment since the beginning of design phase
b. Application security testing process must be coordinated with and approved
by authorized individuals in an organization
c. Vulnerability scans should be performed whenever there are developer
changes to application code or configuration
d. Daily vulnerability scanning for sensitive applications
e. All security flaws should be prioritized, and fixed prior to the release of the
application
f.
Flaws discovered in applications that are already released must be assessed
to determine whether there is a low/medium/high level of exposure due to
the following factors:
i. The likelihood that the security flaw would be exposed
ii. The impact on information security, integrity and application availability
iii. The level of access that would be required to exploit the security flaw
g. Automated escalation workflow of resolving application security flaws
h. Emergency procedures for addressing security flaws must be defined and
NISPG - Version 5.0
Restricted
Page 68
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents