mirror of
https://github.com/MBCProject/mbc-markdown
synced 2026-06-08 11:36:36 +00:00
newsletter update
This commit is contained in:
@@ -47,7 +47,7 @@ Malware Examples
|
||||
|[**Rombertik**](../xample-malware/rombertik.md)|2015|The malware check for sandboxes that suppress errors returned from API routine calls the using ZwGetWriteWatch routine. [[6]](#6)|
|
||||
|
||||
|
||||
Code Snippets
|
||||
<a name="snippet"><a/>Code Snippets
|
||||
-------------
|
||||
**Sandbox Detection::Product Key/ID Testing** (B0007.005) - the value 55274-640-2673064-23950 corresponds to Joe Sandbox.
|
||||
```asm
|
||||
|
||||
@@ -1,16 +1,16 @@
|
||||
# <a name="faq"></a>Malware Behavior Catalog Newsletter #
|
||||
9/9/2022
|
||||
**September 9, 2022**
|
||||
|
||||
Hello all!
|
||||
|
||||
Highlights of recent MBC development include:
|
||||
|
||||
* Released MBC v2.3, which aligns MBC with ATT&CK v11 (plus enhanced descriptions and formatting updates)
|
||||
* Released v22.09 of the STIX 2 representation for MBC v2.3 ([mbc-stix2](https://github.com/MBCProject/mbc-stix2))
|
||||
* Released **MBC v2.3**, which aligns MBC with ATT&CK v11 (plus enhanced descriptions and formatting updates)
|
||||
* Released [v22.09](https://github.com/MBCProject/mbc-stix2) of the STIX 2 representation for MBC v2.3
|
||||
* Updated [capa](https://github.com/fireeye/capa) rules to map to MBC v2.3
|
||||
* Expanded the [malware corpus](../xample-malware/README.md) of mapped malware examples
|
||||
* Expanded MBC's [malware corpus](../xample-malware/README.md) of mapped malware examples
|
||||
* Began meeting with MBC users to understand their use cases
|
||||
|
||||
Next, we'll be considering questions such as whether the MBC's terminology should more closely match ATT&CK's. For example, should MBC "behaviors" instead be referred to as "techniques"? We'll also be adding to the malware corpus, as well as adding code snippets to MBC behavior pages. Please email us at mbc@mitre.org to let us know what you think.
|
||||
Next, we'll be considering questions, such as whether the MBC's terminology should more closely match ATT&CK's. For example, should MBC "behaviors" instead be referred to as "techniques"? We'll also be adding to the malware corpus, as well as adding [code snippets](../anti-behavioral-analysis/sandbox-detection.md/#snippet) to MBC behavior pages. Please email us at mbc@mitre.org to let us know what you think.
|
||||
|
||||
**Please let us know if you're interested in meeting with our team. We'd love to get your feedback and understand your MBC use cases!**
|
||||
Reference in New Issue
Block a user