Abstract

As organizations become increasingly reliant on technology and data, data protection is now a mission critical priority. Ensuring that data is secure and uncorrupted is essential for avoiding downtime, ensuring productivity, and improving performance. Data protection is keeping the data i.e. confidential data secure from being corrupted or being compromised. Securing the data from logs also is essential when talking about data protection. The testing infrastructure which outputs logs may contain IP address as sensitive data, and this may be misused by other employs of the organization. So, by masking it or removing it from logs will make testing infrastructure more secure and testing can be done without interference of other.

Highlights

  • Functional test infrastructure, it is the infrastructure designed to run data domain file system component wise functional test suites

  • The details about client IP are shared once the test scripts are run i.e. IP is visible in console output, in Log files and in yaml file

  • This paper focuses on the “Execute” and “Test” module of a new proposed data masking technique (COBAD) which is based on the statistical content derived from the loaded dataset at aggregated levels

Read more

Summary

Introduction

Functional test infrastructure, it is the infrastructure designed to run data domain file system component wise functional test suites. In Functional test infrastructure, details of IPs are required to run the test scripts. The details about client IP are shared once the test scripts are run i.e. IP is visible in console output, in Log files and in yaml file. A log is a record of the events occurring within an organization’s systems and networks. These log files contain sensitive data like IP address and password of the client. The sensitive data from log is accessible to all the employees of department. To hide this sensitive data from non-admin user, data masking technique is used and is implemented to enhance privacy of sensitive data. There is a risk of tampering the automation scripts by fetching the login credentials from logs

Objectives
Methods
Results
Conclusion
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call