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

[Recorded Future] Incident not created on first launch, but created on second launch #3169

Closed
Lhorus6 opened this issue Dec 19, 2024 · 0 comments · Fixed by #3186
Closed
Assignees
Labels
bug use for describing something not working as expected filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@Lhorus6
Copy link
Contributor

Lhorus6 commented Dec 19, 2024

Description

The connector does not seem to import all alerts at once. By restarting the connector 15 days ago, about a hundred incidents (RF alerts) were recovered, which had not been. The distribution of the 100 new incidents is quite homogeneous, i.e. the missing incidents were a little each day.

Environment

OCTI 6.4.4

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Run the RF connector with this configuration

                 ALERT_DEFAULT_OPENCTI_SEVERITY: 'P3 - low'
                 ALERT_ENABLE: 'False'
                 ALERT_PRIORITY_ALERTS_ONLY: 'True'
                 CONNECTOR_DURATION_PERIOD: PT5M
                 CONNECTOR_NAME: recordedfuture-playbook-alerts
                 CONNECTOR_SCOPE: ipv4-addr,ipv6-addr,vulnerability,domain,url,StixFile
                 CONNECTOR_TYPE: EXTERNAL_IMPORT
                 PLAYBOOK_ALERT_DEBUG: 'False'
                 PLAYBOOK_ALERT_ENABLE: 'True'
                 PLAYBOOK_ALERT_SEVERITY_THRESHOLD_CODE_REPO_LEAKAGE: 'Informational'
                 PLAYBOOK_ALERT_SEVERITY_THRESHOLD_DOMAIN_ABUSE: 'Moderate'
                 PLAYBOOK_ALERT_SEVERITY_THRESHOLD_IDENTITY_NOVEL_EXPOSURES: 'Informational'
                 RECORDED_FUTURE_INITIAL_LOOKBACK: '240'
                 RECORDED_FUTURE_INSIKT_ONLY: 'True'
                 RECORDED_FUTURE_LAST_PUBLISHED_NOTES: '24'
                 RECORDED_FUTURE_PERSON_TO_TA: 'True'
                 RECORDED_FUTURE_PULL_ANALYST_NOTES: 'False'
                 RECORDED_FUTURE_PULL_RISK_LIST: 'False'
                 RECORDED_FUTURE_PULL_SIGNATURES: 'True'
                 RECORDED_FUTURE_PULL_THREAT_MAPS: 'False'
                 RECORDED_FUTURE_RISKLIST_RELATED_ENTITIES: 'Malware,Hash,URL,Threat Actor,MitreAttackIdentifier'
                 RECORDED_FUTURE_RISK_AS_SCORE: 'True'
                 RECORDED_FUTURE_RISK_LIST_THRESHOLD: '70'
                 RECORDED_FUTURE_RISK_THRESHOLD: '58'
                 RECORDED_FUTURE_TA_TO_INTRUSION_SET: 'True'
                 RECORDED_FUTURE_TLP: Green
                 RECORDED_FUTURE_TOKEN: <your_token>
                 RECORDED_FUTURE_TOPIC: VTrvnW,g1KBGl,ZjnoP0,aDKkpk,TXSFt5,UrMRnT,TXSFt3,TXSFt4,ZjnoP2,hPX1cE,UX0YlU,TXSFt1,TXSFt2,UZmDut,irEim2,VlIhvG
    
@Lhorus6 Lhorus6 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Dec 19, 2024
@romain-filigran romain-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Dec 19, 2024
@nino-filigran nino-filigran added the filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. label Dec 20, 2024
@helene-nguyen helene-nguyen self-assigned this Dec 24, 2024
@helene-nguyen helene-nguyen added this to the Bugs backlog milestone Dec 24, 2024
helene-nguyen added a commit that referenced this issue Dec 24, 2024
@helene-nguyen helene-nguyen added the solved use to identify issue that has been solved (must be linked to the solving PR) label Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
4 participants