The triggering event 610 may be based on a timer. The SCS computer system 100 may keep one or more timers to track when to change the network settings. The timer may be for minutes, hours, or days. In some embodiments, the SCS computer system 100 is capable of learning over time and setting the timer based on the system's experience. In some embodiments, the predetermined period of time is stored in persistent memory. The predetermined period of time may also be set by the user, such as through one or more user preferences. The timer causes the SCS computer system 100 to change network settings every predetermined period of time.

The triggering event 610 may be an authentication process. The system 100 may detect an authentication process, either successful or unsuccessful, and decide to update 620 the network settings based on the authentication process. The authentication process may for logging into a machine, accessing a file, and/or connecting to a network. The triggering event 610 may also be exceeding a number of failed attempts, having a login attempt at an unusual time (aka 2 AM), and attempted administrator authentications.

The triggering event 610 may also be an activation of a user button or switch. The button or switch may be hardware or software.

The triggering event 610 may be a program start-up. For example, the SCS computer system 100 may receive an instruction to start a program, such as an encryption suite or virtual private network (VPN). The SCS computer system 100 then updates 620 the network settings before activating the program. The SCS computer system 100 could also update 620 the network settings when the program shuts down or is deactivated.