Bluemont, VA, United States
Bluemont, VA, United States

Verisign, Inc. is an American company based in Reston, Virginia, United States that operates a diverse array of network infrastructure, including two of the Internet's thirteen root nameservers, the authoritative registry for the .com, .net, and .name generic top-level domains and the .cc and .tv country-code top-level domains, and the back-end systems for the .jobs, .gov, and .edu top-level domains. Verisign also offers a range of security services, including managed DNS, Distributed Denial of Service mitigation and cyber-threat reporting.In 2010, Verisign sold its authentication business unit – which included SSL certificate, PKI, Verisign Trust Seal, and Verisign Identity Protection services – to Symantec for $1.28 billion. The deal capped a multi-year effort by Verisign to narrow its focus to its core infrastructure and security business units.Verisign's former CFO Brian Robins announced in August 2010 that the company would move from its original location of Mountain View, California, to Dulles in Northern Virginia by 2011 due to 95% of the company's business being on the East Coast. Wikipedia.


Time filter

Source Type

Patent
VeriSign | Date: 2016-10-17

This present disclosure relates to systems and methods for providing a data plane processing tool chain for processing packets that can use OSI layers 4 and above in the data plane without using a hypervisor. The disclosure has multiple processing capabilities, including: packet filtering, resolving DNS packets, generating packets, packet forwarding, performing DNS look up, time-stamping DNS packets, writing packets to disk, load-balancing, and protecting against DDOS attacks.


Methods and systems for mitigating denial-of-service attacks include a proxy server that monitors a set of application servers configured to receive and service requests from clients. The proxy server intercepts the requests, and in response, provides the clients with customized client-side scripts embedded in markup language. The client-side scripts may include random strings to generate follow-through random uniform resource identifier redirection requests expected by the proxy server. The client-side scripts, upon execution, may challenge the clients by demanding user interaction within a specified period of time, requesting a delay before responding, and/or attempting to set a challenge cookie multiple times. If a client provides the demanded user interaction within the specified time, honors the delay, and/or sets the challenge cookie with the correct value, then the client-side scripts may generate a redirection request expected by the proxy server for that client and the proxy servers may whitelist that client for a configurable duration and forward that clients subsequent requests to the application servers without challenge.


The present invention generally relates to systems and methods for classifying executable files as likely malware or likely benign. The techniques utilize temporally-ordered network behavioral artifacts together with machine learning techniques to perform the classification. Because they rely on network behavioral artifacts, the disclosed techniques may be applied to executable files with obfuscated code.


Systems and methods for tracking malware operator behavior patterns in a network environment simulated for an extended period of time include a processor that causes the system to receive organizational data that describes a virtual organization, obtain additional data related to the organizational data, and provide a simulated computer network of the virtual organization based on the organizational data. The process can further cause the system to install at least one malware on the simulated computer network, monitor one or more interactions between the simulated computer network and an operator of the malware, and build a malware operator profile that characterizes the operator of the malware based on the one or more interactions, with which the operator of the malware can be identified in subsequent interactions.


Systems (100) and methods for enhanced monitoring and adaptive management of inter-network Domain Name System (DNS) traffic include an information capture device (140) in a monitored network. The information capture device receives a redirected connection request originated by a client machine in the monitored network (15) in response to a modified DNS answer from a recursive name server outside of the monitored network, captures detailed information associated with the redirected connection request that is inaccessible to the recursive name server, and sends the captured information to a data storage accessible to the recursive name server for storage as augmented DNS data associated with the client machine and/or the redirected connection request. The information capture device further provides, in response to the redirected connection request, an adaptive answer generated based on the augmented DNS data to the client machine.


System, apparatus, methods, and computer-readable medium for generating a verification code related to a registry operation request are provided. A verification process may be performed to determine if a verification request related to a registry operation is to be approved. If the request is to be approved, a verification code is generated that includes identifying information of a verification service provider (102) and a code indicating that the request has been verified.


Embodiments relate to systems, devices, and computer-implemented methods for providing secure access to a shared registration system of a domain name registry by generating authorization information associated with a domain name, storing (200) the authorization information in an archive, receiving (210), from a non-registrar service provider, a request for access to functionality of a shared registration system of the domain name registry, where the request is associated with the domain name and includes authorization information, determining (220) whether the received authorization information is valid using the archived authorization information, and allowing (250) the non-registrar service provider access to the functionality of the SRS based on a determination that the second authorization information is valid.


Techniques for monitoring zone file changes are presented. The techniques may include obtaining at least one zone change request and parsing the at least one zone change request to obtain at least one change request unit. The techniques may include obtaining a last published zone file, obtaining a new zone file, and comparing the last published zone file to the new zone file to obtain at least one difference object. The techniques may include matching the at least one difference object to the at least one change request unit to identify at least one unmatched difference object. The techniques may include providing a human readable report comprising an indication of the at least one unmatched difference object.


Provided is a method for assigning a time-to-live (TTL) value for a domain name system (DNS) record at a recursive DNS server. The method comprises obtaining, from a client, the TTL value for the DNS record; and storing, in a memory of the recursive DNS server, the TLL value, an identifier of the client, and the DNS record.


In one embodiment, a privacy and security engine enables a user to specify a recursive resolver for a domain name service (DNS) resolution process. The privacy and security engine receives default DNS settings that specify a default recursive resolver to be implemented as a recursive resolver for the DNS resolution process. The default DNS settings are provided by an underlying mobile operator network to which the user device is connected. The privacy and security engine causes the user device to disregard the default DNS settings and implement customized DNS settings that specify a preferred recursive resolver to be implemented as the recursive resolver for the DNS resolution process. The customized DNS settings are associated with an activated privacy and security mode. Unlike conventional approaches to overriding DNS settings, the user is able to specify the recursive resolver that implements the DNS resolution process irrespective of the underlying network.

Loading VeriSign collaborators
Loading VeriSign collaborators