Abstract: Systems and techniques provide activity monitoring and selective obfuscation of various fields or categories of information included in traffic between servers providing services and end-user devices accessing such services. The selective obfuscation may account for a user's role and one or more levels of authorization or permission assigned to such a role. More generally, the disclosed techniques provide the ability to selectively restrict end-user access to data included in server responses, such that desired portions of the data are not accessible while other portions of the data are still accessible. An administrator tool may configure the permissions and rules used to decide whether traffic to or from a particular server or service should be selectively obfuscated; and if so, how that traffic should be selectively obfuscated.

Abstract: The disclosed systems and techniques enable selectively restricting access of an end-user device to traffic. An example method may include training a machine learning (ML) model using a plurality of instances of historical traffic to classify fields included in the plurality of instances into a plurality of categories of information. The method may further include implementing the ML model by: (i) receiving traffic from a server, the traffic responsive to a request from an end-user device; (ii) identifying a field included in the traffic that corresponds to a category of the plurality of categories by applying the ML model to the traffic; (iii) in response to identifying that the field corresponds to the category, selecting a rule corresponding to the category; (iv) modifying the traffic in accordance with the rule to restrict access to information in the field; and (v) transmitting the modified traffic to the end-user device.

Abstract: One or more first servers can implement an example method including storing, at a memory accessible by the first one or more servers, a primary email address for a user. The method further includes detecting a request, from a client device associated with the user, to access a network resource hosted at a second one or more servers, wherein the network resource is associated with an online service. The method also includes automatically generating a secondary email address for the user that is unique to the online service; and transmitting the secondary email address to the second one or more servers such that the online service receives the secondary email address for the user without receiving the primary email address for the user, thereby enabling the online service to transmit emails to the user despite not receiving the primary email address for the user.

Abstract: One or more first servers can implement an example method including storing, at a memory accessible by the first one or more servers, a primary email address for a user. The method further includes detecting a request, from a client device associated with the user, to access a network resource hosted at a second one or more servers, wherein the network resource is associated with an online service. The method also includes automatically generating a secondary email address for the user that is unique to the online service; and transmitting the secondary email address to the second one or more servers such that the online service receives the secondary email address for the user without receiving the primary email address for the user, thereby enabling the online service to transmit emails to the user despite not receiving the primary email address for the user.

Abstract: The disclosed techniques enable selective forwarding and blocking of messages directed to an alias email address based on a whitelist, as well as email alerts triggered by emails from unauthorized senders. More generally, the disclosed techniques enable an enterprise system to store contact emails for users (i.e., alias email addresses) while avoiding storing and managing personal email addresses for the user. For example, the enterprise system may forward personal email addresses to an aliasing server configured to generate alias email addresses based on the personal email addresses. The aliasing server may operate as a “middle man” that receives emails directed to the alias email addresses and that forwards the emails to the personal email addresses (when appropriate). The enterprise system may store and maintain the alias email addresses in lieu of the personal email addresses.

Abstract: The disclosed systems and techniques enable data cycling operations for an aliasing system to refresh first and second copies of aliases maintained by an aliasing server and a server that interacts with end-user devices (e.g., an enterprise server). More generally, the disclosed systems and techniques enable an enterprise system to use alias addresses (e.g., email addresses, phone numbers) for users while avoiding storing and managing the users' personal addresses. For example, the enterprise system may forward personal addresses (e.g., received from a user) to a relay or aliasing server configured to generate alias addresses (e.g., alias email addresses or alias phone numbers) based on the personal addresses. The aliasing server may operate as a “middle man” that receives emails, phone calls, or text messages directed to the alias addresses and that forwards the messages to the personal addresses (when appropriate).

Abstract: One or more first servers can implement an example method including storing, at a memory accessible by the first one or more servers, a primary email address for a user. The method further includes detecting a request, from a client device associated with the user, to access a network resource hosted at a second one or more servers, wherein the network resource is associated with an online service. The method also includes automatically generating a secondary email address for the user that is unique to the online service; and transmitting the secondary email address to the second one or more servers such that the online service receives the secondary email address for the user without receiving the primary email address for the user, thereby enabling the online service to transmit emails to the user despite not receiving the primary email address for the user.

Abstract: The disclosed systems and techniques enable an enterprise system to store contact phone numbers for users while avoiding storing and managing personal phone numbers for the user. For example, the enterprise system may forward personal phone numbers to an aliasing server configured to (i) generate alias phone numbers based on the personal email addresses and (ii) provide the alias phone numbers to the enterprise system. The aliasing server may operate as a “middle man” that receives phone calls or text messages directed to the alias phone numbers and that forwards the phone calls or text messages to the corresponding personal phone numbers (when appropriate). The enterprise system may store and maintain the alias phone numbers in lieu of storing the personal email addresses.

Abstract: The disclosed systems and techniques enable data integrity checks by an enterprise system to verify that a local alias address matches an alias maintained by an aliasing system. More generally, the disclosed systems and techniques enable an enterprise system to use alias addresses (e.g., email addresses, phone numbers) for users while avoiding storing and managing the users' personal addresses. For example, the enterprise system may forward personal addresses (e.g., received from a user) to a relay or aliasing server configured to generate alias addresses (e.g., alias email addresses or alias phone numbers) based on the personal addresses. The aliasing server may operate as a “middle man” that receives emails, phone calls, or text messages directed to the alias addresses and that forwards the messages to the personal addresses (when appropriate).

Abstract: The disclosed techniques enable selective forwarding and blocking of emails directed to an alias email address based on a whitelist, as well as text message alerts triggered by emails from unauthorized senders. More generally, the disclosed techniques enable an enterprise system to store contact emails for users (i.e., alias email addresses) while avoiding storing and managing personal email addresses for the user. For example, the enterprise system may forward personal email addresses to an aliasing server configured to generate alias email addresses based on the personal email addresses. The aliasing server may operate as a “middle man” that receives emails directed to the alias email addresses and that forwards the emails to the personal email addresses (when appropriate). The enterprise system may store and maintain the alias email addresses in lieu of the personal email addresses.

Abstract: The disclosed systems and techniques enable an enterprise system to store contact emails for users while avoiding storing and managing personal email addresses for the user. For example, the enterprise system may forward personal email addresses to an aliasing server configured to generate alias email addresses based on the personal email addresses. The aliasing server may operate as a “middle man” that receives emails directed to the email addresses and that forwards the emails to the personal email addresses (when appropriate). The enterprise system may store and maintain the alias email addresses in lieu of storing the personal email addresses.

Abstract: The disclosed techniques enable selective forwarding and blocking of text messages directed to an alias phone number based on a whitelist, as well as text message alerts triggered by text messages from unauthorized originating numbers. More generally, the disclosed techniques enable an enterprise system to store contact phone numbers (i.e., alias phone numbers) for users while avoiding storing and managing personal phone numbers for the user. For example, the enterprise system may forward personal phone numbers to an aliasing server configured to generate alias phone numbers based on the personal phone number. The aliasing server may operate as a “middle man” that receives text messages directed to the alias phone number and that forwards the text messages to the personal phone number when appropriate. The enterprise system may store and maintain the alias phone numbers in lieu of the personal phone numbers.

Abstract: The disclosed techniques enable selective forwarding and blocking of text messages directed to an alias phone number based on a whitelist, as well as email alerts triggered by text messages from unauthorized originating numbers. More generally, the disclosed techniques enable an enterprise system to store contact phone numbers (i.e., alias phone numbers) for users while avoiding storing and managing personal phone numbers for the user. For example, the enterprise system may forward personal phone numbers to an aliasing server configured to generate alias phone numbers based on the personal phone number. The aliasing server may operate as a “middle man” that receives text messages directed to the alias phone number and that forwards the text messages to the personal phone number when appropriate. The enterprise system may store and maintain the alias phone numbers in lieu of the personal phone numbers.

Abstract: Selective forwarding and blocking of calls directed to an alias phone number based on a whitelist, as well as email alerts triggered by phone calls from unauthorized originating numbers. More generally, the disclosed techniques enable an enterprise system to store contact phone numbers (i.e., alias phone numbers) for users while avoiding storing and managing personal phone numbers for the user. For example, the enterprise system may forward personal phone numbers to an aliasing server configured to generate alias phone numbers based on the personal phone number. The aliasing server may operate as a “middle man” that receives calls directed to the alias phone number and that forwards the calls to the personal phone number when appropriate. The enterprise system may store and maintain the alias phone numbers in lieu of the personal phone numbers.

Abstract: The disclosed techniques enable selective forwarding and blocking of calls directed to an alias phone number based on a whitelist, as well as text message alerts triggered by phone calls from unauthorized originating numbers. More generally, the disclosed techniques enable an enterprise system to store contact phone numbers (i.e., alias phone numbers) for users while avoiding storing and managing personal phone numbers for the user. For example, the enterprise system may forward personal phone numbers to an aliasing server configured to generate alias phone numbers based on the personal phone number. The aliasing server may operate as a “middle man” that receives calls directed to the alias phone number and that forwards the calls to the personal phone number when appropriate. The enterprise system may store and maintain the alias phone numbers in lieu of the personal phone numbers.