diff --git a/docs/installation/configuration/authentication.md b/docs/installation/configuration/authentication.md index 3698c7dbe..2631524e0 100644 --- a/docs/installation/configuration/authentication.md +++ b/docs/installation/configuration/authentication.md @@ -43,21 +43,17 @@ The authentication section (`auth:`) of the configuration files contains all the - .* - .*@localhost ldap: - admin_dn: null auto_create: true auto_sync: true base: ou=people,dc=assemblyline,dc=local bind_pass: null bind_user: null - classification_mappings: {} email_field: mail enabled: false group_lookup_query: (&(objectClass=Group)(member=%s)) image_field: jpegPhoto image_format: jpeg name_field: cn - signature_importer_dn: null - signature_manager_dn: null uid_field: uid uri: ldap://localhost:389 oauth: @@ -218,9 +214,6 @@ Here is an example configuration block to add to your configuration file that wi # Should LDAP be enabled or not? enabled: true - # DN of the group or the user who will get admin privileges - admin_dn: cn=admin_staff,ou=people,dc=planetexpress,dc=com - # Auto-create users if they are missing, this means # that if a user exists in LDAP, Assemblyline will create an # account for it upon the first login @@ -230,6 +223,20 @@ Here is an example configuration block to add to your configuration file that wi # email, name... with the LDAP server upon each login? auto_sync: true + # Automatic role and classification assignments + auto_properties: + # any user with a @localhost.local email will be given + # TLP:Amber classification and any user with a @example.com + # email will be made administrator in the system + - field: email + pattern: .*@localhost\.local$ + type: classification + value: "TLP:A" + - field: email + pattern: .*@example\.com$ + type: role + value: "admin" + # Base DN for the users base: ou=people,dc=planetexpress,dc=com @@ -239,8 +246,6 @@ Here is an example configuration block to add to your configuration file that wi # User use to query the LDAP server bind_user: null - classification_mappings: {} - # Name of the field containing the email address email_field: mail @@ -256,12 +261,6 @@ Here is an example configuration block to add to your configuration file that wi # Name of the field containing the user's name name_field: cn - # DN of the group or the user who will get signature_importer role - signature_importer_dn: null - - # DN of the group or the user who will get signature_manager role - signature_manager_dn: null - # Field name for the UID uid_field: uid diff --git a/docs/installation/configuration/config_file.md b/docs/installation/configuration/config_file.md index e2d910106..13067e7a1 100644 --- a/docs/installation/configuration/config_file.md +++ b/docs/installation/configuration/config_file.md @@ -51,7 +51,6 @@ The full specification of the file [is defined here](https://github.com/Cybercen base: ou=people,dc=assemblyline,dc=local bind_pass: null bind_user: null - classification_mappings: {} email_field: mail enabled: false group_lookup_query: (&(objectClass=Group)(member=%s)) @@ -59,8 +58,6 @@ The full specification of the file [is defined here](https://github.com/Cybercen image_field: jpegPhoto image_format: jpeg name_field: cn - signature_importer_dn: null - signature_manager_dn: null uid_field: uid uri: ldap://localhost:389 oauth: @@ -390,7 +387,6 @@ The full specification of the file [is defined here](https://github.com/Cybercen - Networking - Internet Connected - Dynamic Analysis - sha256_sources: [] tag_types: attribution: - attribution.actor diff --git a/docs/user_manual/submitting_sha256.fr.md b/docs/user_manual/submitting_sha256.fr.md index 63225701a..31a2e289b 100644 --- a/docs/user_manual/submitting_sha256.fr.md +++ b/docs/user_manual/submitting_sha256.fr.md @@ -18,7 +18,7 @@ Entrez le hash SHA256 que vous souhaitez analyser dans la zone de texte "URL/SHA Lorsque vous soumettez un hash SHA256, Assemblyline vérifie si le hash correspond à un fichier précédemment rencontré. Si un fichier correspondant est trouvé, il est resoumis pour une analyse plus approfondie. Dans le cas contraire, si le fichier n'est pas trouvé dans le stockage local, Assemblyline tentera de le localiser sur une source externe, telle que Malware Bazaar, et le soumettra pour analyse s'il est trouvé. -Ce comportement dépend de votre configuration de déploiement — consultez [`submission.sha256_sources`](../../odm/models/config/#sha256source) pour les détails de configuration. +Ce comportement dépend de votre configuration de déploiement — consultez [`submission.file_sources`](../../odm/models/config/#filesource) pour les détails de configuration. ## Options diff --git a/docs/user_manual/submitting_sha256.md b/docs/user_manual/submitting_sha256.md index e11a59273..4ec05505c 100644 --- a/docs/user_manual/submitting_sha256.md +++ b/docs/user_manual/submitting_sha256.md @@ -18,7 +18,7 @@ Enter the SHA256 hash you want to analyze into the "URL/SHA256 To Scan" textbox When you submit a SHA256 hash, Assemblyline checks if the hash matches any file previously encountered. If a match is found, it resubmits the file for further analysis. Alternatively, if the file isn't found in the local store, Assemblyline will attempt to locate it on an external source, such as Malware Bazaar, and submit it for analysis if found. -This behavior depends on your deployment configuration—see [`submission.sha256_sources`](../../odm/models/config/#sha256source) for setup details. +This behavior depends on your deployment configuration—see [`submission.file_sources`](../../odm/models/config/#filesource) for setup details. ## Options