Skip to content

Conversation

@clement-fouque
Copy link
Contributor

@clement-fouque clement-fouque commented Aug 11, 2024

Proposed commit message

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

@clement-fouque clement-fouque marked this pull request as ready for review August 12, 2024 07:40
@clement-fouque
Copy link
Contributor Author

@elastic/security-service-integrations should this integration be owned by your team as it’s linked to vulnerabilities/CVE?

@andrewkroh andrewkroh added the New Integration Issue or pull request for creating a new integration package. label Aug 13, 2024
@kcreddy
Copy link
Contributor

kcreddy commented Aug 20, 2024

should this integration be owned by your team as it’s linked to vulnerabilities/CVE?

@jamiehynds @narph can you confirm if this new integration should belong to us?

@jamiehynds
Copy link

should this integration be owned by your team as it’s linked to vulnerabilities/CVE?

@jamiehynds @narph can you confirm if this new integration should belong to us?

Hey @kcreddy - we're fine to review and publish, but should list the owner type as community.

@kcreddy kcreddy added the Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] label Aug 20, 2024
@kcreddy
Copy link
Contributor

kcreddy commented Aug 20, 2024

@clement-fouque the CI is failing on missing codeowners for this integration.
Can you add this integration to .github/CODEOWNERS file and the owner as @elastic/security-service-integrations.

Please also update your manifest.yml to reflect same change and @jamiehynds comment above:

owner:
  github: elastic/security-service-integrations
  type: community

@clement-fouque
Copy link
Contributor Author

Thank you @jamiehynds and @kcreddy. I'll implement those changes.

@clement-fouque
Copy link
Contributor Author

@kcreddy please let me know if there are any pending tasks from my side. Thanks.

Copy link
Contributor

@kcreddy kcreddy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to add pipeline or system tests?

Also, if there are any conflicting review comments between me and Andrew's review, please apply changes suggested by Andrew. There might be few in titles and descriptions.

@clement-fouque clement-fouque requested a review from a team as a code owner September 3, 2024 21:01
@clement-fouque clement-fouque changed the title First EPSS integration creation [first_epss] New integration Sep 3, 2024
@elasticmachine
Copy link

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@clement-fouque
Copy link
Contributor Author

I've implemented all suggestions/remarks. Please let me know if there is anything else.

Copy link
Contributor

@kcreddy kcreddy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some suggestions. Overall LGTM 👍🏼

Comment on lines +43 to +47
- date:
field: json.date
tag: date_date
formats: [yyyy-MM-dd]
target_field: first_epss.vulnerability.date
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After this date processor you can assign the value to @timestamp so that it gets value from the event.

Reference: https://github.com/elastic/integrations/blob/main/packages/prisma_access/data_stream/event/elasticsearch/ingest_pipeline/default.yml#L4506-L4510

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kcreddy I'm not sure I want to do this as this date corresponds to the time when First EPSS generated this data but not when it was ingested. We might have a gap up to 24 hours between the generated data and the ingestion.

As timestamp is the main date to "control" search, I think it's better to keep it as it is.

@elasticmachine
Copy link

💚 Build Succeeded

History

cc @clement-fouque

@elastic-sonarqube
Copy link

@clement-fouque
Copy link
Contributor Author

Can I squash and merge or should I wait from someone from the Integration team ?

@andrewkroh
Copy link
Member

@kreddy Can you take one final look and then please handle the merge with a well formed commit message like we aim for 😄 . Thanks.

@kcreddy kcreddy merged commit f62ba53 into elastic:main Sep 6, 2024
@elasticmachine
Copy link

Package first_epss - 0.1.0 containing this change is available at https://epr.elastic.co/search?package=first_epss

@andrewkroh andrewkroh added the Integration:first_epss First EPSS (Community supported) label Sep 6, 2024
harnish-crest-data pushed a commit to chavdaharnish/integrations that referenced this pull request Feb 4, 2025
Create new integration package First EPSS.

Adds `vulnerability` datastream to collect exploit prediction score data 
from the First EPSS API.

- Adds the ingest pipeline for `vulnerability` data stream.
- Maps fields according to the ECS schema and added custom fields.
- Adds dashboard.
- Adds README.
- Adds test for pipeline for `vulnerability` data stream.
- Adds system test cases for `vulnerability` data stream.
harnish-crest-data pushed a commit to chavdaharnish/integrations that referenced this pull request Feb 5, 2025
Create new integration package First EPSS.

Adds `vulnerability` datastream to collect exploit prediction score data 
from the First EPSS API.

- Adds the ingest pipeline for `vulnerability` data stream.
- Maps fields according to the ECS schema and added custom fields.
- Adds dashboard.
- Adds README.
- Adds test for pipeline for `vulnerability` data stream.
- Adds system test cases for `vulnerability` data stream.
@andrewkroh andrewkroh added maintainer:Community Community supported integration and removed Community labels Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Integration:first_epss First EPSS (Community supported) maintainer:Community Community supported integration New Integration Issue or pull request for creating a new integration package. Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants