[PATCH] Implement some other ONYPHE simple APIs (but still not the search API)

[onyphe]

Implement some other ONYPHE simple APIs (but still not the search API)

Request Type

Feature

Work Environment

N/A

Description

Implements user, onionscan, sniffer, ctl and md5 simple APIs. But not the search APIs yet. Unfortunately, as we are not at easy with Python, we just sent the patch for onyphe_api.py and not for onyphe_analyzer.py.
onyphe-patch.txt

[nadouani]

Hello @onyphe

do you think we need a custom analyzer template for each one of these new methods? or we just need to add an analyzer for user, onionscan, sniffer, ctl and md5, an reuse the existing report templates for TheHive?

Thanks

[onyphe]

Hello, well, as we are not the original developers of the Cortex Analyzer and we don't have a real experience on how that works internally, it is quite difficult to answer your question. My guess would be to use the same scheme as previously used for other methods, as there is no difference in regards to our APIs. So, I would say, go for a new analyzer for each new API. Field names are normalized between APIs, if that may help you take the right decision. Best regards,

…

-- https://www.onyphe.io Your Internet SIEM Twitter: @onyphe On 17/12/2018 13:38, Nabil Adouani wrote: Hello @onyphe<https://github.com/onyphe> do you think we need a custom analyzer template for each one of these new methods? or we just need to add an analyzer for user, onionscan, sniffer, ctl and md5, an reuse the existing report templates for TheHive? Thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#372 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Amv11mnQl5lvL9nJVPaATeWTGFRfL_Xcks5u55BUgaJpZM4YYfaH>.

[nadouani]

Fair enough, I'll ping the person who've written the 5-6 initial analyzers.

Thanks

[dadokkio]

@onyphe is this issue still valid?

[onyphe]

Hello,

as we have moved to APIv2, this should not be a concern anymore.

Thank you,