{
	"id": "11b3bfe9-8972-4a05-a62b-52fbe61ee939",
	"created_at": "2026-04-06T03:36:55.272999Z",
	"updated_at": "2026-04-10T03:20:48.159037Z",
	"deleted_at": null,
	"sha1_hash": "0e0800c6431de37a34bcf03cdad75d68b5c2afe8",
	"title": "Increase scheduling priority",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 41282,
	"plain_text": "Increase scheduling priority\r\nBy Archiveddocs\r\nArchived: 2026-04-06 03:15:16 UTC\r\nApplies To: Windows Vista, Windows Server 2008, Windows 7, Windows 8.1, Windows Server 2008 R2,\r\nWindows Server 2012 R2, Windows Server 2012, Windows 8\r\nThis security policy reference topic for the IT professional describes the best practices, location, values, policy\r\nmanagement, and security considerations for this policy setting.\r\nThis policy setting determines which user accounts can increase the base priority class of a process. It is not a\r\nprivileged operation to increase relative priority within a priority class. This user right is not required by\r\nadministrative tools that are supplied with the operating system, but it might be required by software development\r\ntools.\r\nSpecifically, this security setting determines which accounts can use a process with Write Property access to\r\nanother process to increase the run priority that is assigned to the other process. A user with this privilege can\r\nchange the scheduling priority of a process through the Task Manager user interface.\r\nThis policy setting is supported on versions of Windows that are designated in the Applies To list at the beginning\r\nof this topic.\r\nConstant: SeIncreaseBasePriorityPrivilege\r\nUser-defined list of accounts\r\nNot defined\r\nAdministrators\r\n1. Allow the default value, Administrators, as the only account responsible for controlling process scheduling\r\npriorities.\r\nGPO_name\\Computer Configuration\\Windows Settings\\Security Settings\\Local Policies\\User Rights Assignment\r\nBy default this setting is Administrators on domain controllers and on stand-alone servers.\r\nThe following table lists the actual and effective default policy values for the most recent supported versions of\r\nWindows. Default values are also listed on the policy’s property page.\r\nhttps://technet.microsoft.com/library/dn221960.aspx\r\nPage 1 of 3\n\nServer type or GPO Default value\r\nDefault Domain Policy Not defined\r\nDefault Domain Controller Policy Administrators\r\nStand-Alone Server Default Settings Administrators\r\nDomain Controller Effective Default Settings Administrators\r\nMember Server Effective Default Settings Administrators\r\nClient Computer Effective Default Settings Administrators\r\nThere are no differences in the way this policy setting works between the supported versions of Windows that are\r\ndesignated in the Applies To list at the beginning of this topic.\r\nThis section describes features, tools, and guidance to help you manage this policy.\r\nA restart of the computer is not required for this policy setting to be effective.\r\nAny change to the user rights assignment for an account becomes effective the next time the owner of the account\r\nlogs on.\r\nSettings are applied in the following order through a Group Policy Object (GPO), which will overwrite settings on\r\nthe local computer at the next Group Policy update:\r\n1. Local policy settings\r\n2. Site policy settings\r\n3. Domain policy settings\r\n4. OU policy settings\r\nWhen a local setting is greyed out, it indicates that a GPO currently controls that setting.\r\nThis section describes how an attacker might exploit a feature or its configuration, how to implement the\r\ncountermeasure, and the possible negative consequences of countermeasure implementation.\r\nhttps://technet.microsoft.com/library/dn221960.aspx\r\nPage 2 of 3\n\nA user who is assigned this user right could increase the scheduling priority of a process to Real-Time, which\r\nwould leave little processing time for all other processes and could lead to a denial-of-service condition.\r\nVerify that only Administrators have the Increase scheduling priority user right assigned to them.\r\nNone. Restricting the Increase scheduling priority user right to members of the Administrators group is the\r\ndefault configuration.\r\nUser Rights Assignment\r\nSource: https://technet.microsoft.com/library/dn221960.aspx\r\nhttps://technet.microsoft.com/library/dn221960.aspx\r\nPage 3 of 3",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://technet.microsoft.com/library/dn221960.aspx"
	],
	"report_names": [
		"dn221960.aspx"
	],
	"threat_actors": [
		{
			"id": "d90307b6-14a9-4d0b-9156-89e453d6eb13",
			"created_at": "2022-10-25T16:07:23.773944Z",
			"updated_at": "2026-04-10T02:00:04.746188Z",
			"deleted_at": null,
			"main_name": "Lead",
			"aliases": [
				"Casper",
				"TG-3279"
			],
			"source_name": "ETDA:Lead",
			"tools": [
				"Agentemis",
				"BleDoor",
				"Cobalt Strike",
				"CobaltStrike",
				"RbDoor",
				"RibDoor",
				"Winnti",
				"cobeacon"
			],
			"source_id": "ETDA",
			"reports": null
		}
	],
	"ts_created_at": 1775446615,
	"ts_updated_at": 1775791248,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/0e0800c6431de37a34bcf03cdad75d68b5c2afe8.pdf",
		"text": "https://archive.orkl.eu/0e0800c6431de37a34bcf03cdad75d68b5c2afe8.txt",
		"img": "https://archive.orkl.eu/0e0800c6431de37a34bcf03cdad75d68b5c2afe8.jpg"
	}
}