Hi Liam,
Yesterday, I successfully developed own custom rc_cts package by using existing/developed (rc_cts_abuseipdb) cts packages.
Here is my learnings:
- Created an rc_cts package strcture properly like below.
- .\rc-cts-xxxxxx - \.rc_cts_xxxxxx - \.components - __init__.py - xxxxxx_threat_searcher.py - __init__.py - setup.py - tox.ini- Change the setup.py configuration. (entry_points) #threat service & component names #gen_config
- xxxxx_threat_searcher.py
- def config_section_data() : This config data automatically update in app.config
- Create *class rc_cts_searcher* class.
- channel = searcher_channel("xxxxx_customthreatservicename") #sudo resutil threatserviceedit -name "xxxxx_customthreatservicename"
- @handler("Input Artifact type Ex: net.ip etc")
- Define lookup/query/result functions according your requirement.
- xxxx.append(xxxx.append( Hit( Outputdata ))) & return the (xxxx). (xxxx = values)
Thanks,
Santhosh Baswa
------------------------------
SANTHOSH BASWA
------------------------------
Original Message:
Sent: Mon October 07, 2019 10:30 AM
From: Liam Mahoney
Subject: rc_cts package (development)
Santhosh,
I'm about to attempt to create my own CTS and I have the same question.
I've found documentation that states that the rc_cts package isn't the most robust way to create CTSes here.
I was considering looking into creating the CTS with Django, but if rc_cts makes it easier I would probably just roll with that.
------------------------------
Liam Mahoney
------------------------------