Best Practices Cyber Security Testing
Best Practices Cyber Security Testing
Abstract
In a post COVID-19 world, the need to become digitally-enabled is more
pressing than ever before. Enterprises are accelerating digital strategies and
omni-channel transformation projects. But while they expand their digital
footprint to serve customers and gain competitive advantage, the number
and extent of exposure to external threats also increases exponentially.
This is due to the many moving parts in the technology stack such as cloud,
big data, legacy modernization, and microservices. This paper looks at the
security vulnerabilities in open systems interconnection (OSI) layers and
explains the best practices for embedding cyber security testing seamlessly
into organizations.
Introduction
Open systems interconnection (OSI) comprises many layers, each of which has its own services/protocols. These can be used by hackers and
attackers to compromise the system through different types of attacks.
Application Layer File transfer protocol, simple mail SQL injecon, Cross-site scripng so
ware a
ack
transfer protocol, Domain Name System (persistent and non-persistent), Cross-site request
forgery, Cookie poisoning
TCP, UDP, SSL, TLS - protocols Port scanning, ping flood and Distributed Denial-of-
Transport Layer
Service (DDoS) a
ack
For some OSI layers like Transport, Session, 4. Understanding the vulnerabilities in from SVN or GIT (version control
Presentation, and Application, some infrastructure security testing systems)
amount of exposure can be controlled
5. Understanding roles and responsibilities • Code is automatically pushed for
using robust application-level security
for cloud security testing scanning after applying UI and server-
practices and cyber security testing. From
based pre-scan filters. Code is scanned
a quality engineering perspective, it is for vulnerability
important for testers to be involved in the Best practice 1: Defining and
• Results are pushed to the software
digital security landscape. executing a digital tester’s
security center database for
While there is no single approach to handle role in the DevSecOps model verification
cyber security testing, the following five DevSecOps means dealing with security
best practices can ensure application • If there are no vulnerabilities, the
aspects as code (security as a code). It
code is pushed to quality assurance
security by embedding cyber security enables two aspects, namely, ‘secure code’
(QA) and production stages. If
testing seamlessly into organizations: delivered ‘at speed’. Here is how security-as-
vulnerabilities are found, these are
1. Defining and executing a digital tester’s a-code works:
backlogged for resolution
role in the DevSecOps model • Code is delivered in small chunks.
DevSecOps can be integrated to
2. Understanding and implementing Possible changes are submitted in perform security tests on networks,
data security testing practices in non- advance to identify vulnerabilities digital applications and identity access
production environments • The application security team management portals. The tests focus on
3. Security in motion – Focusing on triggers scheduled scans in the build how to break into the system and expose
dynamic application security testing environment. Code checkout happens vulnerable areas.
References
1. https://www.marketsandmarkets.com/Market-Reports/security-testing-market-150407261.html
2. https://www.infosys.com/services/validation-solutions/service-offerings/security-testing-validation-services.html
© 2021 Infosys Limited, Bengaluru, India. All Rights Reserved. Infosys believes the information in this document is accurate as of its publication date; such information is subject to change without notice. Infosys
acknowledges the proprietary rights of other companies to the trademarks, product names and such other intellectual property rights mentioned in this document. Except as expressly permitted, neither this
documentation nor any part of it may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, printing, photocopying, recording or otherwise, without the
prior permission of Infosys Limited and/ or any named intellectual property rights holders under this document.