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.

Sign up for GitHub

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

Jump to bottom

[Backport 2.x] Ask for mapping of threat intel feeds related fields only when threat intel is enabled #869

Merged
merged 1 commit into from
Feb 7, 2024
Merged

[Backport 2.x] Ask for mapping of threat intel feeds related fields only when threat intel is enabled #869

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions ...ages/CreateDetector/components/ConfigureFieldMapping/containers/ConfigureFieldMapping.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -276,9 +276,14 @@ export default class ConfigureFieldMapping extends Component<
mappingsView.response.properties[ruleFieldName].path;
});
let threatIntelFeedFields = new Set();
mappingsView.response.threat_intel_field_aliases?.forEach(({ fields }) => {
fields.forEach((field) => threatIntelFeedFields.add(field));
});

// Only if threat_intel is enabled, we want to show the relevant fields for mapping
if (this.state.detector.threat_intel_enabled) {
mappingsView.response.threat_intel_field_aliases?.forEach(({ fields }) => {
fields.forEach((field) => threatIntelFeedFields.add(field));
});
}

mappingsView.response.unmapped_field_aliases?.forEach((ruleFieldName) => {
if (
!ruleFieldsForEnabledRules.has(ruleFieldName) &&
Expand Down
Loading