SecEdit.exe

File Path: C:\Windows\system32\SecEdit.exe
Description: Windows Security Configuration Editor Command Tool

Hashes

Type	Hash
MD5	`FE961D8056062E047BCFBD77EBD431B7`
SHA1	`2CD7718827C793F8CA53C9FE0CC11D09E450EA67`
SHA256	`58348E21FB9AE1582E68AA07BF21F87D58DB03FE12123B0DF5BFB3A7E168DB26`
SHA384	`FA57EEE9D6F92DCAD9C55C6B62ED419AB2908222C94F94AE7AC058B5F76B479F1A58AB23BC5BD7FA5A185F452E643E31`
SHA512	`C4EE99BA9AD4E3B725404E564628196A0F68DE0C46D267C29FB33007C850A9A79875D007AE12C946E4BA34398B29183327438DC63A23D3F97F8D0702C32B142A`
SSDEEP	`768:TjqyEE2/b/6zzHDn82pvU14B+uKGWzdJqT7/pXk:NEE2D/6zzjvUmhKGWz6`
IMP	`58A66C69176097C9B8C5C9AE4273BD6F`
PESHA1	`B71284E44F41E4B89B1754A814E26BEA3E416B87`
PE256	`30CE15333529587515D7A886CAEAB19B4E5EAF379707DB09DF81B7CA372FCE7D`

Runtime Data

Usage (stdout):

The syntax of this command is:

secedit [/configure | /analyze | /import | /export | /validate | /generaterollback]

Loaded Modules:

Path
C:\Windows\System32\KERNEL32.DLL
C:\Windows\System32\KERNELBASE.dll
C:\Windows\SYSTEM32\ntdll.dll
C:\Windows\system32\SecEdit.exe

Signature

Status: Signature verified.
Serial: 3300000266BD1580EFA75CD6D3000000000266
Thumbprint: A4341B9FD50FB9964283220A36A1EF6F6FAA7840
Issuer: CN=Microsoft Windows Production PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Subject: CN=Microsoft Windows, O=Microsoft Corporation, L=Redmond, S=Washington, C=US

File Metadata

Original Filename: SeCEdit
Product Name: Microsoft Windows Operating System
Company Name: Microsoft Corporation
File Version: 10.0.19041.1 (WinBuild.160101.0800)
Product Version: 10.0.19041.1
Language: English (United States)
Legal Copyright: Microsoft Corporation. All rights reserved.
Machine Type: 64-bit

File Scan

VirusTotal Detections: 0/75
VirusTotal Link: https://www.virustotal.com/gui/file/58348e21fb9ae1582e68aa07bf21f87d58db03fe12123b0df5bfb3a7e168db26/detection

File Similarity (ssdeep match)

File	Score
C:\Windows\system32\SecEdit.exe	33
C:\WINDOWS\system32\SecEdit.exe	32
C:\WINDOWS\system32\SecEdit.exe	35
C:\Windows\system32\SecEdit.exe	36
C:\windows\system32\SecEdit.exe	33
C:\Windows\SysWOW64\SecEdit.exe	36
C:\WINDOWS\SysWOW64\SecEdit.exe	38
C:\windows\SysWOW64\SecEdit.exe	38
C:\WINDOWS\SysWOW64\SecEdit.exe	36
C:\Windows\SysWOW64\SecEdit.exe	40
C:\Windows\SysWOW64\SecEdit.exe	41

Additional Info*

*The information below is copied from MicrosoftDocs, which is maintained by Microsoft. Available under CC BY 4.0 license.

secedit commands

Configures and analyzes system security by comparing your current security configuration against specified security templates.

[!NOTE] The Microsoft Management Console (MMC) and the Security Configuration and Analysis snap-in are not available on Server Core.

Syntax

secedit /analyze
secedit /configure
secedit /export
secedit /generaterollback
secedit /import
secedit /validate

Parameters

Parameter	Description
secedit /analyze	Allows you to analyze current systems settings against baseline settings that are stored in a database. The analysis results are stored in a separate area of the database and can be viewed in the Security Configuration and Analysis snap-in.
secedit /configure	Allows you to configure a system with security settings stored in a database.
secedit /export	Allows you to export security settings stored in a database.
secedit /generaterollback	Allows you to generate a rollback template with respect to a configuration template.
secedit /import	Allows you to import a security template into a database so that the settings specified in the template can be applied to a system or analyzed against a system.
secedit /validate	Allows you to validate the syntax of a security template.

Remarks

If there is no filepath specified, all filenames will default to the current directory.
Your analysis results are stored in a separate area of the database and can be viewed in the Security Configuration and Analysis snap-in to the MMC.

If your security templates are created by using the Security Template snap-in, and if you run the Security Configuration and Analysis snap-in against those templates, the following files are created:

File	Description
scesrv.log	<ul><li>Location: `%windir%\security\logs`</li><li>Created by: Operating system</li><li>File type: Text</li><li>Refresh rate: Overwritten when `secedit analyze`, `secedit configure`, `secedit export` or `secedit import` is run.</li><li>Content: Contains the results of the analysis grouped by policy type.</li></ul>
user-selected name.sdb	<ul><li>Location: `%windir%\<user account>\Documents\Security\Database`</li><li>Created by: Running the Security Configuration and Analysis snap-in</li><li>File type: Proprietary</li><li>Refresh rate: Updated whenever a new security template is created.</li><li>Content: Local security policies and user-created security templates.</li></ul>
user-selected name.log	<ul><li>Location: User-defined, but defaults to `%windir%\<user account>\Documents\Security\Logs`</li><li>Created by: Running the `secedit analyze` or `secedit configure` commands, or by using the Security Configuration and Analysis snap-in.</li><li>File type: Text</li><li>Refresh rate: Overwritten when `secedit analyze` or `secedit configure` is run, or by using the Security Configuration and Analysis snap-in.</li><li>Content: Log file name, date and time, and the results of the analysis or investigation.</li></ul>
user-selected name.inf	<ul><li>Location: `%windir%\<user account>\Documents\Security\Templates`</li><li>Created by:* Running the Security Template snap-in.</li><li>File type: Text</li><li>Refresh rate: Overwritten each time the security template is updated.</li><li>Content: Contains the set up information for the template for each policy selected using the snap-in.</li></ul>

Additional References

Command-Line Syntax Key