semvec/pypi-packages huggingface dataset:
rc-cts 45.1.3279
Resilient Circuits Custom Threat Service
License: MIT

# Resilient Lightweight Custom Threat Service

This package implements the Custom Threat Service API, providing a
simple framework to develop threat source lookups in Python using the
Resilient Circuits integration framework.

It's suitable for simple "lightweight" threat source lookups.
* All lookups are asynchronous.
* There is currently no support for file-attachment handling.
* Queries are not stored persistently, so if you need to track external resources
  (for example, if your threat service starts a long-running task such as
  sandbox processing) those will not be tracked across restarts.

For more robust and advanced features, you should consider deploying
a standalone threat service, for example based on the Django example
(https://github.com/ibmresilient/resilient-python-examples/tree/master/django-custom-threat-service).

## What's new
v42 supports resutil threatserviceedit -user and -password authentication

## Environment

This package requires that it is installed on a RHEL platform and that the resilient-circuits application is running.
Install this package with 'pip', or `python setup.py install`.
To set the config values in the app.config file run `resilient-circuits config -u`.

Config values example:
```
[custom_threat_service]

# Base URL for threat services API
urlbase=/cts

# Whether we support file upload (for "file"-type artifacts)
# upload_file=False

# Retry time indicators
#first_retry_secs=5
#later_retry_secs=60
#max_retries=60

# Cache management
#cache_size=10000
#cache_ttl=600000

# use auth_user and auth_password when specifying the -user and -password parameters on
#  resutil threatserviceedit to ensure basic authentication
#auth_user=
#auth_password=
```

Run with: `resilient-circuits run`.

## Custom Threat Service Example

This package includes an **example** threat service that responds to 'URL' artifacts with
static data.  To register the example onto your Resilient server (assuming that the
`resilient-circuits` application is running on the same server):

```
sudo resutil threatserviceedit -name example -resturl http://127.0.0.1:9000/cts/example
sudo resutil threatservicetest -name example
```
To delete,
```
sudo resutil threatservicedel -name example
```
rc-webserver 45.1.3279
Resilient Circuits Web Server Component
License: MIT

# Resilient Circuits Web Server

Provides a Web server that can be extended by additional components.
This is useful for implementing a Threat Service, or for webhooks.

To have your Python method called with requests at `/path/endpoint`, 
* Make a class that inherits from `circuits.web.BaseController`,
* Set `self.channel="path"`,
* Use the `rc_webserver.web.@exposeWeb` decorator on a method, e.g. `@exposeWeb("endpoint")`.

## Changelog

2020-07-15: version 37.2

* Updated for python 3.

## Environment

This package requires that it is installed on a RHEL platform and that the resilient-circuits application is running.
Install this package with 'pip', or `python setup.py install`.
To set the config values in the app.config file run `resilient-circuits config -u`.

Config values example:
```
[webserver]

# IP or DNS for the web server. Default is localhost.
# server=0.0.0.0

# Port for the web server. Default is 9000.
# port=9000

# Set the web server to use secure protocol. secure=1 means HTTPS, and secure=0 means HTTP. Default is 0
# secure=1

# The cert file is the private key certificate for the TLS server. This is required if secure=1. Default is None.
# certfile=~/.resilient/ssl.cer
```

Run with: `resilient-circuits run`.