You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/en/connecting_your_tools/parsers/file/ms_defender.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,7 @@ toc_hide: true
5
5
This parser helps to parse Microsoft Defender Findings and supports two types of imports:
6
6
- You can import a JSON output file from the api/vulnerabilities/machinesVulnerabilities endpoint of Microsoft defender.
7
7
- You can upload a custom zip file which include multiple JSON files from two Microsoft Defender Endpoints. For that you have to make your own zip file and include two folders (machines/ and vulnerabilities/) within the zip file. For vulnerabilities/ you can attach multiple JSON files from the api/vulnerabilities/machinesVulnerabilities REST API endpoint of Microsoft Defender. Furthermore, in machines/ you can attach the JSON output from the api/machines REST API endpoint of Microsoft Defender. Then, the parser uses the information in both folders to add more specific information like the affected IP Address to the finding.
8
+
<br>However, if you have a fast changing environment with a huge number of vulnerabilities and endpoints, it is recommended to leave the folder machines/ empty. Then, for stability reasons the machine info is skipped and only the machineID is added to the finding.
8
9
9
10
### Sample Scan Data
10
11
Sample MS Defender Parser scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/ms_defender).
Copy file name to clipboardExpand all lines: dojo/db_migrations/0027_jira_issue_type_settings.py
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
# Generated by Django 2.2.4 on 2020-01-02 15:33
2
2
3
+
fromdjango.confimportsettings
3
4
fromdjango.dbimportmigrations, models
4
5
5
6
@@ -13,6 +14,6 @@ class Migration(migrations.Migration):
13
14
migrations.AlterField(
14
15
model_name='jira_conf',
15
16
name='default_issue_type',
16
-
field=models.CharField(choices=[('Task', 'Task'), ('Story', 'Story'), ('Epic', 'Epic'), ('Spike', 'Spike'), ('Bug', 'Bug'), ('Security', 'Security')], default='Bug', help_text='You can define extra issue types in settings.py', max_length=15),
17
+
field=models.CharField(choices=settings.JIRA_ISSUE_TYPE_CHOICES_CONFIG, default='Bug', help_text='You can define extra issue types in settings.py', max_length=15),
Copy file name to clipboardExpand all lines: dojo/db_migrations/0182_alter_jira_instance_default_issue_type.py
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
# Generated by Django 4.1.7 on 2023-03-06 11:38
2
2
3
+
fromdjango.confimportsettings
3
4
fromdjango.dbimportmigrations, models
4
5
5
6
@@ -13,6 +14,6 @@ class Migration(migrations.Migration):
13
14
migrations.AlterField(
14
15
model_name='jira_instance',
15
16
name='default_issue_type',
16
-
field=models.CharField(choices=[('Task', 'Task'), ('Story', 'Story'), ('Epic', 'Epic'), ('Spike', 'Spike'), ('Bug', 'Bug'), ('Security', 'Security')], default='Bug', help_text='You can define extra issue types in settings.py', max_length=255),
17
+
field=models.CharField(choices=settings.JIRA_ISSUE_TYPE_CHOICES_CONFIG, default='Bug', help_text='You can define extra issue types in settings.py', max_length=255),
0 commit comments