package server

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message Alert

nemesis.proto:22

Used by containers to signal the "alerting" container

message Analysis

nemesis.proto:1139

Used in: FileDataEnriched

message AppSettings

nemesis.proto:713

Used in: ParsedData

message Archive

nemesis.proto:821

Used in: ParsedData

message Archive.ArchiveEntry

nemesis.proto:822

Used in: Archive

message AuthenticationDataIngestion

nemesis.proto:88

Data that may be used to authenticate to a resource. The resource does not need to be accessible over a network and a local resource may be specified using the file:// scheme in the URI parameter. The type data may be anything that may be used to authenticate such as a password, certificate, JWT, SAML token, TGT, NTLM hash, private key, etc. The authentication data does not need to be additionally encoded because all ODR string parameters already support hex encoding values. ODR: `authentication_data`, defined in docs/odr/references/authentication_data.md See authentication_data.md for supported "type" values.

Used in: AuthenticationDataIngestionMessage

message AuthenticationDataIngestionMessage

nemesis.proto:110

message Canaries

nemesis.proto:1497

Used in: FileDataEnriched

message Canaries.Canary

nemesis.proto:1498

Used in: Canaries

message ChromiumCookie

nemesis.proto:1211

Used in: ChromiumCookieMessage

message ChromiumCookieMessage

nemesis.proto:1235

message ChromiumCookiesFile

nemesis.proto:1036

Used in: ParsedData

message ChromiumDownload

nemesis.proto:1169

Used in: ChromiumDownloadMessage

message ChromiumDownloadMessage

nemesis.proto:1181

message ChromiumHistoryEntry

nemesis.proto:1152

Used in: ChromiumHistoryMessage

message ChromiumHistoryFile

nemesis.proto:1019

Used in: ParsedData

message ChromiumHistoryMessage

nemesis.proto:1163

message ChromiumLogin

nemesis.proto:1187

Used in: ChromiumLoginMessage

message ChromiumLoginMessage

nemesis.proto:1205

message ChromiumLoginsFile

nemesis.proto:1028

Used in: ParsedData

message ChromiumStateFile

nemesis.proto:1044

Used in: ChromiumStateFileMessage, ParsedData

message ChromiumStateFileMessage

nemesis.proto:1241

message ConnectionString

nemesis.proto:700

Used in: AppSettings, WebConfig

message CookieIngestion

nemesis.proto:420

Used in: CookieIngestionMessage

message CookieIngestionMessage

nemesis.proto:466

message DatabaseCredential

nemesis.proto:693

Used in: ConnectionString

message Dll

nemesis.proto:759

Used in: Imports

message DomainCachedCredential

nemesis.proto:841

Used in: RegHiveSecurity

message DotnetAnalysis

nemesis.proto:1120

Used in: Analysis

message DotnetAnalysis.GadgetCall

nemesis.proto:1121

Used in: DotnetAnalysis

message DotnetAssembly

nemesis.proto:806

Used in: ParsedData

message DpapiBlob

nemesis.proto:1313

Used in: DpapiBlobMessage

message DpapiBlobMessage

nemesis.proto:1345

message DpapiCredentialAttribute

nemesis.proto:951

not yet used

https://github.com/fortra/impacket/blob/8799a1a2c42ad74423841d21ed5f4193ea54f3d5/impacket/dpapi.py#L850-L862

Used in: DpapiCredentialFile

message DpapiCredentialFile

nemesis.proto:960

Used in: ParsedData

enum DpapiCredentialFile.CREDENTIAL_FLAGS

nemesis.proto:962

https://github.com/fortra/impacket/blob/8799a1a2c42ad74423841d21ed5f4193ea54f3d5/impacket/dpapi.py#L196-L204

Used in: DpapiCredentialFile

enum DpapiCredentialFile.CREDENTIAL_PERSIST

nemesis.proto:974

https://github.com/fortra/impacket/blob/8799a1a2c42ad74423841d21ed5f4193ea54f3d5/impacket/dpapi.py#L216-L220

Used in: DpapiCredentialFile

enum DpapiCredentialFile.CREDENTIAL_TYPE

nemesis.proto:981

https://github.com/fortra/impacket/blob/8799a1a2c42ad74423841d21ed5f4193ea54f3d5/impacket/dpapi.py#L206=L214

Used in: DpapiCredentialFile

message DpapiDomainBackupkey

nemesis.proto:1253

Used in: DpapiDomainBackupkeyMessage

message DpapiDomainBackupkeyMessage

nemesis.proto:1263

message DpapiMasterkey

nemesis.proto:1270

also used in ParsedData

Used in: DpapiMasterkeyMessage, ParsedData

message DpapiMasterkeyMessage

nemesis.proto:1307

message Error

nemesis.proto:16

Generic Error message

message EvtxFile

nemesis.proto:1060

Used in: ParsedData

message Exports

nemesis.proto:756

Used in: DotnetAssembly, Pe

message ExtractedHash

nemesis.proto:1592

Hashes extracted from processed files

Used in: ExtractedHashMessage

message ExtractedHashMessage

nemesis.proto:1629

message FileDataEnriched

nemesis.proto:1510

Used in: FileDataEnrichedMessage

message FileDataEnrichedMessage

nemesis.proto:1585

message FileDataIngestion

nemesis.proto:121

The content of a specific file system resource. The path must be in a UNC, file system, or mapped path format. File system and mapped paths must be absolute and use forward slashes for separators (e.g. /). Paths are expected to be canonicalized but there is no verification of this. ODR: `file_data`, defined in file_data.md

Used in: FileDataIngestionMessage

message FileDataIngestionMessage

nemesis.proto:135

message FileDataPlaintext

nemesis.proto:1635

Used in: FileDataPlaintextMessage

message FileDataPlaintextChunkMessage

nemesis.proto:1677

message for text chunks extracted from a FileDataPlaintext document has simplified metadata since it goes straight back to the NLP service after extraction

message FileDataPlaintextMessage

nemesis.proto:1669

message FileDataSourcecode

nemesis.proto:1695

Used in: FileDataSourcecodeMessage

message FileDataSourcecodeMessage

nemesis.proto:1719

message FileHashes

nemesis.proto:1505

Used in: FileDataEnriched

message FileInformationIngestion

nemesis.proto:151

Information about a specific file system resource. Note that file_info is more specialized than the path_list submission which may include information about non-file system resources (ex. registry paths). The path must be in a UNC, file system, or mapped path format. File system and mapped paths must be absolute and use forward slashes for separators (e.g. /). Paths are expected to be canonicalized but there is no verification of this. Submission parameters may accommodate files from most operating systems. The only submission parameters that are required is the file path and type. Note that all date time parameters in ODRs including for the modified, access, and creation times for Windows files are expected to be UTC.

Used in: FileInformationIngestionMessage

message FileInformationIngestionMessage

nemesis.proto:189

message GroupPolicyPreferences

nemesis.proto:640

Used in: ParsedData

message GroupPolicyPreferences.GroupPolicyPreferencesEntry

nemesis.proto:641

Used in: GroupPolicyPreferences

nemesis.proto:740

Used in: DotnetAssembly, Pe

message ImplMapEntry

nemesis.proto:802

Used in: DotnetAssembly

message Imports

nemesis.proto:763

Used in: DotnetAssembly, Pe

message JWTToken

nemesis.proto:687

Used in: AppSettings

message LSASecret

nemesis.proto:866

Used in: RegHiveSecurity

message Lnk

nemesis.proto:552

Used in: ParsedData

message McafeeSitelist

nemesis.proto:656

Used in: ParsedData

message McafeeSitelist.McafeeSitelistEntry

nemesis.proto:657

Used in: McafeeSitelist

message Metadata

nemesis.proto:43

Metadata header that's send with every message to the API ODR: defined in README.md

Used in: AuthenticationDataIngestionMessage, ChromiumCookieMessage, ChromiumDownloadMessage, ChromiumHistoryMessage, ChromiumLoginMessage, ChromiumStateFileMessage, CookieIngestionMessage, DpapiBlobMessage, DpapiDomainBackupkeyMessage, DpapiMasterkeyMessage, ExtractedHashMessage, FileDataEnrichedMessage, FileDataIngestionMessage, FileDataPlaintextMessage, FileDataSourcecodeMessage, FileInformationIngestionMessage, MetadataHeader, NamedPipeIngestionMessage, NetworkAddressIngestionMessage, NetworkConnectionIngestionMessage, PathListIngestionMessage, ProcessEnrichedMessage, ProcessIngestionMessage, ProcessMessage, RawDataIngestionMessage, RegistryValueIngestionMessage, RouteDataIngestionMessage, ServiceEnrichedMessage, ServiceIngestionMessage, TimeDataIngestionMessage

message MetadataHeader

nemesis.proto:74

message NamedPipeIngestion

nemesis.proto:398

Information about Windows named pipes.

Used in: NamedPipeIngestionMessage

message NamedPipeIngestionMessage

nemesis.proto:414

message NetworkAddressIngestion

nemesis.proto:1771

Addresses that may be used to refer to the host the agent is running on or a network resource on the host. Addresses are expected to conform to the public standard for the address type but there is no verification of this. As an example, ethernet addresses are expected to use a hyphen as a separator instead of a colon as per IEEE 802.3 but this is not verified.

Used in: NetworkAddressIngestionMessage

message NetworkAddressIngestionMessage

nemesis.proto:1782

message NetworkConnectionIngestion

nemesis.proto:488

Connections between the host the agent is running with itself or another host. These could also be listening ports (i.e., netstat output) Addresses are expected to conform to the public standard for the address type but there is no verification of this as well. As an example, ethernet addresses are expected to use a hyphen as a separator instead of a colon as per IEEE 802.3 but this is not verified. The protocol list and matching source and destination lists represent the protocol stack used for a connection. The lists only need to represent a portion of the protocol stack and do not need to represent the entirety of it. The lists allow the ODR to be reused for any connection type an operator may be interested in without having to make a new ODR for each new connection type. local_address is treated as source, remote_address is treated as destination

Used in: NetworkConnectionIngestionMessage

message NetworkConnectionIngestionMessage

nemesis.proto:510

message NoseyParker

nemesis.proto:1406

Protobuf representation of NoseyParker JSON output

Used in: FileDataEnriched, FileDataPlaintext

message NoseyParker.BlobMetadata

nemesis.proto:1444

Used in: Matches

message NoseyParker.End

nemesis.proto:1418

Used in: Source_span

message NoseyParker.Location

nemesis.proto:1428

Used in: Matches

message NoseyParker.Matches

nemesis.proto:1451

Used in: RuleMatches

message NoseyParker.Offset_span

nemesis.proto:1408

Used in: Location

message NoseyParker.Provenance

nemesis.proto:1439

Used in: Matches

message NoseyParker.RuleMatches

nemesis.proto:1462

Used in: NoseyParker

message NoseyParker.Snippet

nemesis.proto:1433

Used in: Matches

message NoseyParker.Source_span

nemesis.proto:1423

Used in: Location

message NoseyParker.Start

nemesis.proto:1413

Used in: Source_span

message OfficeDocNew

nemesis.proto:610

.docx/.pptx/.xlsx/etc.

Used in: ParsedData

message OfficeDocOle

nemesis.proto:590

.doc/.ppt/.xls/etc.

Used in: ParsedData

message ParsedData

nemesis.proto:1069

Represents any file data type specifically parsed by Nemesis This is the container for the above section of messages

Used in: FileDataEnriched

message Passwd

nemesis.proto:567

Used in: ParsedData

message Passwd.PasswdEntry

nemesis.proto:568

Used in: Passwd

message PathListIngestion

nemesis.proto:346

Child listings for a specified path. The path must be in a UNC, URI, file system, or mapped path format. File system and mapped paths must be absolute and use forward slashes for separators (e.g. /). Paths are expected to be canonicalized but there is no verification of this. The mapped file format may be used to specify a registry keys as well using PowerShell convention of specifying the hive name as the drive (ex. HKLM:).

Used in: PathListIngestionMessage

message PathListIngestionMessage

nemesis.proto:353

message Pdf

nemesis.proto:625

Used in: ParsedData

message Pe

nemesis.proto:781

Used in: ParsedData

message Principal

nemesis.proto:196

Used in ProcessIngestion

Used in: Token

message Process

nemesis.proto:1725

Used in: ProcessMessage

message ProcessCategory

nemesis.proto:1377

Used in: ProcessEnriched

message ProcessEnriched

nemesis.proto:1385

Used in: ProcessEnrichedMessage

message ProcessEnrichedMessage

nemesis.proto:1399

message ProcessIngestion

nemesis.proto:246

Information about the currently running processes for the host the agent is running on. The file_name parameter must be in a UNC, file system, or mapped path format. File system and mapped paths must be absolute and use forward slashes for separators (e.g. /). Paths are expected to be canonicalized but there is no verification of this. Submission parameters may accommodate processes information for most operating systems. The only submission parameter that is required is the process id. Note that all start time parameters are expected to be from the Unix epoch.

Used in: ProcessEnriched, ProcessIngestionMessage

message ProcessIngestionMessage

nemesis.proto:274

message ProcessMessage

nemesis.proto:1753

message RawDataIngestion

nemesis.proto:285

Data that may consist of anything. Developers and operators may use this type to push arbitrary data to the ODS to take advantage of any builtin or custom automated post processing the ODS performs. Example use cases include daily status reports, C2 logs, and other data that may be unique to the workflow of a team.

Used in: RawDataIngestionMessage

message RawDataIngestionMessage

nemesis.proto:295

message RawParsedData

nemesis.proto:945

RawParsedData is for unstructured data meant for the user instead of an automated pipeline

Used in: ParsedData

message RegHiveSam

nemesis.proto:929

Used in: ParsedData

message RegHiveSecurity

nemesis.proto:882

Used in: ParsedData

message RegHiveSystem

nemesis.proto:837

Used in: ParsedData

message RegistryValueIngestion

nemesis.proto:301

Used in: RegistryValueIngestionMessage

enum RegistryValueIngestion.RegistryValueKind

nemesis.proto:302

Used in: RegistryValueIngestion

message RegistryValueIngestionMessage

nemesis.proto:334

message Resource

nemesis.proto:792

Used in DotnetAssembly - TODO: combine into one block

Used in: DotnetAssembly

message RouteDataIngestion

nemesis.proto:1792

Network routing rules for the host the agent is running on. The network mask must be specified separately from the destination address. Addresses and network masks are also expected to conform to the public standard for the address type but there is no verification of this.

Used in: RouteDataIngestionMessage

message RouteDataIngestionMessage

nemesis.proto:1808

message SamHash

nemesis.proto:905

Used in: RegHiveSam

message ServiceEnriched

nemesis.proto:1357

Used in: ServiceEnrichedMessage

message ServiceEnrichedMessage

nemesis.proto:1371

message ServiceIngestion

nemesis.proto:360

Information about Windows services.

Used in: ServiceEnriched, ServiceIngestionMessage

message ServiceIngestionMessage

nemesis.proto:391

message Shadow

nemesis.proto:579

Used in: ParsedData

message Shadow.ShadowEntry

nemesis.proto:580

Used in: Shadow

message Signature

nemesis.proto:735

Used in: DotnetAssembly, Pe

message SlackDownloads

nemesis.proto:535

Used in: ParsedData

message SlackDownloads.SlackDownload

nemesis.proto:536

Used in: SlackDownloads

message SlackWorkspaces

nemesis.proto:523

Used in: ParsedData

message SlackWorkspaces.SlackWorkspace

nemesis.proto:524

Used in: SlackWorkspaces

message Symbol

nemesis.proto:751

Used in: Dll, Exports

message TimeDataIngestion

nemesis.proto:1823

Used in: TimeDataIngestionMessage

message TimeDataIngestionMessage

nemesis.proto:1836

message Token

nemesis.proto:203

Used in: Process, ProcessIngestion

enum Token.ImpersonationLevel

nemesis.proto:216

Used in: Token

message Token.TokenPrivilege

nemesis.proto:204

Used in: Token

enum Token.TokenType

nemesis.proto:211

Used in: Token

message Tomcat

nemesis.proto:676

Used in: ParsedData

message Tomcat.TomcatEntry

nemesis.proto:677

Used in: Tomcat

message Typeref

nemesis.proto:798

Used in: DotnetAssembly

message UserTime

nemesis.proto:1818

Current time information about the host the agent is running on. The subparameters of the Users list must delimited by spaces in CSV submissions. Note that all date time parameters are expected to be in UTC from the Unix epoch regardless of what time zone the host uses.

Used in: TimeDataIngestion

enum VerificationFlags

nemesis.proto:720

Used in Pe - TODO: combine into one block?

Used in: Signature

message VersionInfo

nemesis.proto:766

Used in: DotnetAssembly, Pe

message WebConfig

nemesis.proto:708

Used in: ParsedData

message YaraMatches

nemesis.proto:1477

Used in: FileDataEnriched

message YaraMatches.YaraMatch

nemesis.proto:1487

Used in: YaraMatches

message YaraMatches.YaraStringMatch

nemesis.proto:1483

Used in: YaraMatch

message YaraMatches.YaraStringMatchInstance

nemesis.proto:1478

Used in: YaraStringMatch