src/Lifecycle.php
public function protectGlobals() {
		// TODO: Merge whitelist from config
		$whitelist = [
			"_COOKIE" => ["XDEBUG_SESSION"],
		];
		$globalsAfterRemoval = Protection::removeGlobals(
			$GLOBALS,
			$whitelist
		);
		Protection::overrideInternals(
			$globalsAfterRemoval,
			$_ENV,
			$_SERVER,
			$_GET,
			$_POST,
			$_FILES,
			$_COOKIE,
			$_SESSION
		);
	}
public function protectGlobals() {
		// TODO: Merge whitelist from config
		$whitelist = [
			"_COOKIE" => ["XDEBUG_SESSION"],
		];
		$globalsAfterRemoval = Protection::removeGlobals(
			$GLOBALS,
			$whitelist
		);
		Protection::overrideInternals(
			$globalsAfterRemoval,
			$_ENV,
			$_SERVER,
			$_GET,
			$_POST,
			$_FILES,
			$_COOKIE,
			$_SESSION
		);
	}
public function protectGlobals ( ) { // TODO: Merge whitelist from config $ whitelist = [ "_COOKIE" => [ "XDEBUG_SESSION" ] , ] ; $ globalsAfterRemoval = Protection :: removeGlobals ( $ GLOBALS , $ whitelist ) ; Protection :: overrideInternals ( $ globalsAfterRemoval , $ _ENV , $ _SERVER , $ _GET , $ _POST , $ _FILES , $ _COOKIE , $ _SESSION ) ; }
By default, PHP passes all sensitive user information around in global variables,
available for reading and modification in any code, including third party libraries.

All global variables are replaced with objects that alert the developer of their
protection and encapsulation through GlobalStub objects.

@see https://php.gt/globals
By default PHP passes all sensitive user information around in global variables available for reading and modification in any code including third party libraries .