Providing application security using causal graph

1. A method for providing application security using a path profile, including:

receiving, from a first remote device, a first request to access a first location of a website;

transmitting, to a server that corresponds to the website, the first request to access the first location;

receiving, from the server, a first cookie that includes identifying information for the first location;

in response to receiving the first cookie, storing the identifying information for the first location;

receiving, from the first remote device, a second request to access a second location of the website, wherein:

the second location is distinct from the first location, and

the second request includes the identifying information for the first location;

transmitting, to the server, the second request to access the second location;

receiving, from the server, a second cookie that includes the identifying information for the first location and identifying information for the second location;

in response to receiving the second cookie, storing a first path profile that includes the identifying information for the first location and the identifying information for the second location;

receiving, from a second remote device, a third request to access the second location of the website;

determining whether the third request meets request criteria based on the first path profile;

in accordance with a determination that the third request meets the request criteria, transmitting, to the server, the third request to access the second location; and

in accordance with a determination that the third request does not meet the request criteria, performing one or more enforcement operations.

2. The method of claim 1 , including storing a plurality of path profiles that include at least the first path profile and a second path profile.

3. The method of claim 2 , including using the plurality of path profiles to generate at least one path pattern.

4. The method of claim 3 , wherein the at least one path pattern includes a pattern that indicates a tier-to-tier traversal of the website.

5. The method of claim 2 , including:

for a respective path profile of the plurality of path profiles, determining whether the respective path profile includes a first path characteristic; and

in accordance with a determination that the respective path profile includes the first path characteristic, incrementing a counter that corresponds to the first path characteristic.

6. The method of claim 1 , wherein:

the third request meets the request criteria when the third request includes the identifying information for the first location;

the third request does not meet the request criteria when the third request does not include the identifying information for the first location.

7. The method of claim 1 , wherein:

the third request meets the request criteria when the third request includes the identifying information for the second location;

the third request does not meet the request criteria when the third request does not include the identifying information for the second location.

8. The method of claim 1 , wherein the one or more enforcement operations include delaying or forgoing transmission of the third request to access the second location.

9. The method of claim 1 , wherein the one or more enforcement operations include transmitting information associated with the third request to an enforcement analysis module.

10. The method of claim 1 , wherein the one or more enforcement operations include modifying the third request, wherein the modified third request is a request to access an alternative location that is distinct from the requested second location.

11. The method of claim 1 , wherein the one or more enforcement operations include determining whether a stored invalid request value meets invalidation criteria.

12. The method of claim 1 , wherein:

the second location corresponds to an application programming interface (API) call;

the third request meets the request criteria when the third request includes API call information that corresponds to the second location; and

the third request does not meet the request criteria when the third request does not include the API call information that corresponds to the second location.

13. The method of claim 1 , wherein:

the website includes a root domain level and a plurality of subdomain levels;

the second location corresponds to a respective subdomain level of the plurality of subdomain levels;

the third request meets the request criteria when the third request includes identifying information associated with the respective subdomain level; and

the third request does not meet the request criteria when the third request does not include identifying information associated with the respective subdomain level.

14. The method of claim 1 , wherein the first cookie includes first time information and the second cookie includes second time information; and

the method includes, in response to receiving the second cookie, storing the second time information.

15. The method of claim 1 , wherein storing the identifying information for the first location and the second location includes storing a hash of the second cookie.

16. A system, comprising:

memory;

one or more processors; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for:

receiving, from a first remote device, a first request to access a first location of a web site;

transmitting, to a server that corresponds to the web site, the first request to access the first location;

receiving, from the server, a first cookie that includes identifying information for the first location;

in response to receiving the first cookie, storing the identifying information for the first location;

receiving, from the first remote device, a second request to access a second location of the website, wherein:

the second location is distinct from the first location, and

the second request includes the identifying information for the first location;

transmitting, to the server, the second request to access the second location;

receiving, from the server, a second cookie that includes the identifying information for the first location and identifying information for the second location;

in response to receiving the second cookie, storing a first path profile that includes the identifying information for the first location and the identifying information for the second location, and storing second time information, wherein the first cookie includes first time information and the second cookie includes the second time information.

17. The system of claim 16 , wherein the one or more programs include instructions for:

receiving, from a second remote device, a third request to access the second location of the web site;

determining whether the third request meets request criteria;

in accordance with a determination that the third request meets the request criteria, transmitting, to the server, the third request to access the second location; and

in accordance with a determination that the third request does not meet the request criteria, performing one or more enforcement operations.

18. The system of claim 17 , wherein the one or more enforcement operations include delaying or forgoing transmission of the third request to access the second location.

19. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by an electronic device, cause the device to:

receive, from a first remote device, a first request to access a first location of a website;

transmit, to a server that corresponds to the website, the first request to access the first location;

receive, from the server, a first cookie that includes identifying information for the first location;

in response to receiving the first cookie, store the identifying information for the first location;

receive, from the first remote device, a second request to access a second location of the website, wherein:

the second location is distinct from the first location, and

the second request includes the identifying information for the first location;

transmit, to the server, the second request to access the second location;

receive, from the server, a second cookie that includes the identifying information for the first location and identifying information for the second location;

in response to receiving the second cookie, store a first path profile that includes the identifying information for the first location and the identifying information for the second location;

wherein storing the identifying information for the first location and the second location includes storing a hash of the second cookie.