This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
@yasinmnk you can use Amazon fire hose if you want to filter the logs
before sending it to SecOps [1] along with lambda functions. If you want
to use bindplane, you'll need to filter the logs via a processor [2] and
add it between the source and dest...
Hi! Bindplane has the following documentation to ingest from an S3
bucket : https://bindplane.com/docs/resources/sources/aws-s3-event you
will need to create an SQS queue. Google SecOps already supports this
natively, you can either configure an SQS ...
Hi @Aswin_Asokan The Organization details is visible to all users in
SecOps and it is not controlled by a permission. If you'd like to have a
feature to hide this from your users, please open a feature request with
us via a support case.
Hi @devashishsingh You can look into using the dataTables.patch method
to update the data tables via the chronicle API :
https://cloud.google.com/chronicle/docs/reference/rest/v1alpha/projects.locations.instances.dataTables/patch
Hi @Avish_garg ! Thank you for the question. Currently the SecOps URL is
not configurable directly. You can raise a support case for us to create
a new URL ( that can either replace the existing URL or create a
secondary domain) for your use. Please ...