Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output Standardization?? #99

Open
cccs-rs opened this issue Jun 19, 2023 · 0 comments · May be fixed by #101
Open

Output Standardization?? #99

cccs-rs opened this issue Jun 19, 2023 · 0 comments · May be fixed by #101

Comments

@cccs-rs
Copy link

cccs-rs commented Jun 19, 2023

Hi from Canada🍁,

I was wondering if malduck has any output standard to try and normalize the data from the various parsers?

I've noticed other authors using your framework (like c3rb3ru5d3d53c's mwcfg-modules) have documented their parsers and their output but it would be nice to have something working within the engine to perform this kind of data validation/normalization so that it would apply to any parsers written under this framework.

I've been working on creating a one-stop-shop Python library (configextractor-py, used by a service within Assemblyline) that would be able to run any parser and render the output according to the CCCS' MACO standard. At present, it supports the MACO and MWCP frameworks (we're currently working on CAPE support as well) and I would love to add official support for malduck parsers!

If you guys do happen to have an output standard, would you mind pointing me in the right direction? If not, could I entice you to consider the MACO standard 😉?

If you have any question/comments/concerns, feel free to ask and thank you again for your work on this project! 🦆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant