{'fraction_non_alphanumeric': 0.018425460636515914, 'fraction_numerical': 0.0008375209380234506, 'mean_word_length': 5.2565445026178015, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Implementation of IPSec Protocol

The aim of this paper is to present the implementation of IPSec Protocol. IPSec protocol provides an end user to end user traffic with ensuring authenticity and confidentiality of data packet. IP sec is a successor of the ISO standard Network Layer Security Protocol (NLSP). NLSP was based on the SP3 protocol that was published by NIST, but designed by the Secure Data Network System project of the National Security Administration (NSA). IPSec is officially specified by the Internet Engineering Task Force (IETF) in a series of Request for Comments addressing various components and extensions, including the official capitalization style of the term. IPSec defines encryption, authentication and key management routines for ensuring the privacy, integrity and authenticity of data in a VPN as the information traverses public IP networks. Because IPSec requires each end of the tunnel to have a unique address, special care must be taken when implementing IPSec VPNs in environments using private IP addressing based on network address translation. Fortunately, several vendors offer solutions to this problem. However, they add more management complexity.