admin/MBCProject-mbc-markdown
1
0
Fork 0
mirror of https://github.com/MBCProject/mbc-markdown synced 2026-06-08 11:36:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update 09092022.md

Browse Source
This commit is contained in:
Ryan Xu
2022-09-08 15:09:06 -04:00
committed by GitHub
parent d5791ce5fe
commit 9937ebd631
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ynewsletters/09092022.md
+3 -3
View File
@@ -8,9 +8,9 @@ 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](https://github.com/MBCProject/mbc-stix2/tree/v22.09) of the STIX 2 representation for MBC v2.3
* Updated [capa](https://github.com/fireeye/capa) rules to map to MBC v2.3
* Expanded MBC's [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 expanding 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.
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 expanding 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!**
**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!**