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

connector state null #61

Open
NaufalIhsan2002 opened this issue Jun 21, 2024 · 9 comments
Open

connector state null #61

NaufalIhsan2002 opened this issue Jun 21, 2024 · 9 comments
Assignees

Comments

@NaufalIhsan2002
Copy link

NaufalIhsan2002 commented Jun 21, 2024

can anyone help me? my connector doesn't working
Capture
Capture2
is there something wrong with my configuration?

@misje
Copy link
Owner

misje commented Jun 21, 2024

Do you have anything that indicates that it isn't working? This is an enrichment connector, so it will only perform work when a new entity is ingested into your platform. Alternatively, you can enrich an entity manually (see the documentation in the Usage section).

The state field is not used for enrichment connectors. I believe they are only used by stream connectors, possibly other types.

I'll take this cause confusion into consideration when updating the manual.

@NaufalIhsan2002
Copy link
Author

NaufalIhsan2002 commented Jun 21, 2024

i have try to manually enrich but i got this error. what should i do?
Capture3
Capture 4JPG

@misje
Copy link
Owner

misje commented Jun 21, 2024

You most likely have a self-signed certificate in OpenSearch (which is the norm). You will have to skip TLS verification. See important settings in the documentation. The env. var. would be WAZUH_OPENSEARCH_VERIFY_TLS=false.

@NaufalIhsan2002
Copy link
Author

NaufalIhsan2002 commented Jun 21, 2024

im sorry but can you help me one more time
Capture5
do my manual enrichment working right?
Capture6
i also have error like this

@misje
Copy link
Owner

misje commented Jun 21, 2024

Your last screenshot is not an error. Have a look in the documentation:

As for your errors in the previous runs, please provide information about what they say, and I will try to help.

@NaufalIhsan2002
Copy link
Author

Capture9
is it normal that the operations complete and total number of operation is 0?
image
i run docker compose logs -f --tail=100 connector-wazuh, and i got this.

im sorry for bothering you so much. i really want to learn this

@misje
Copy link
Owner

misje commented Jun 21, 2024

It appears that you are enriching indicators. As I pointed out earlier with the references to the documentation, enriching indicators only work if those indicators have relationships to observables, as there is no direct STIX indicator pattern support. The only workaround I can offer for now, is using automation to create these relationships automatically.

is it normal that the operations complete and total number of operation is 0?

It is if there is nothing for the connector to do, or if the indicator was not found in Wazuh. It only creates STIX objects when the search is performed, and results are found.

@misje misje self-assigned this Jun 23, 2024
@NaufalIhsan2002
Copy link
Author

image
image
do i have to manually make incident or the connector make incident automatically?

i also trying to search for "Wazuh SIEM" in opencti and i can't found it. can you help me please?

@misje
Copy link
Owner

misje commented Jun 26, 2024

do i have to manually make incident or the connector make incident automatically?

Incidents are created depending on your configuration. See the documentation on the topic.

i also trying to search for "Wazuh SIEM" in opencti and i can't found it. can you help me please?

This is an identity of type system. You'll find this under "systems" in OpenCTI, and linked to in all incidents.

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

No branches or pull requests

2 participants