msgid "Either specify the search terms in the url, or POST a json array / xml (with the root element being \"request\" and specify the correct accept and content type headers."
msgid "Either specify the search terms in the url, or POST a json array / xml (with the root element being \"request\" and specify the correct headers based on content type."
msgid "No x509 certificate or GnuPG key set in your profile. To receive attributes in emails, submit your public certificate or GnuPG key in your profile."
msgid "Either specify the search terms in the url, or POST a json or xml with the filter parameters. Valid filters: id (event ID), tags (list of tags), from (from date in YYYY-MM-DD format), to (to date in YYYY-MM-DD format), last (events with a published timestamp newer than - valid options are in time + unit format such as 6d or 2w, etc)"
msgid "Distribution level 5 is not supported when uploading a sample without passing an event ID. Distribution level 5 is meant to take on the distribution level of an existing event."
msgid "Organisation could not be deleted. Generally organisations should never be deleted, instead consider moving them to the known remote organisations list. Alternatively, if you are certain that you would like to remove an organisation and are aware of the impact, make sure that there are no users or events still tied to this organisation before deleting it."
msgid "Couldn't save the new organisation, are you sure that the uuid is in the correct format? Also, make sure the organisation's name doesn't clash with an existing one."
msgid "Not authorised. This is either due to an invalid auth key, or due to the sync user not having authentication permissions enabled on the remote server. Another reason could be an incorrect sync server setting."
msgstr ""
#: Controller/ServersController.php:1187
msgid "File not found."
msgstr "파일을 찾을 수 없습니다."
#: Controller/ServersController.php:1193
msgid "File could not be deleted."
msgstr "파일을 삭제할 수 없습니다."
#: Controller/ServersController.php:1213;1229
msgid "Upload failed."
msgstr "업로드 실패."
#: Controller/ServersController.php:1221
msgid "File already exists. If you would like to replace it, remove the old one first."
msgstr "이미 존재하는 파일입니다. 교체하길 원하신다면, 먼저 기존 파일을 삭제해주세요."
#: Controller/ShadowAttributesController.php:195
msgid "Moving of the file that this attachment references failed."
msgstr ""
#: Controller/ShadowAttributesController.php:259
msgid "Could not discard proposal."
msgstr ""
#: Controller/ShadowAttributesController.php:311
msgid "Attribute has not been added: attachments are added by \"Add attachment\" button"
msgid "Delete of file attachment failed. Please report to administrator."
msgstr ""
#: Model/Attribute.php:748
msgid "The entered string is too long and would get truncated. Please consider adding the data as an attachment instead"
msgstr ""
#: Model/Attribute.php:858
msgid "Checksum has an invalid length or format (expected: %s hexadecimal characters). Please double check the value or select type \"other\"."
msgstr ""
#: Model/Attribute.php:865
msgid "Checksum has an invalid length or format (expected: at least 35 hexadecimal characters). Please double check the value or select type \"other\"."
msgstr ""
#: Model/Attribute.php:872
msgid "The input doesn't match the expected sha1 format (expected: 40 hexadecimal characters). Keep in mind that MISP currently only supports SHA1 for PEhashes, if you would like to get the support extended to other hash types, make sure to create a github ticket about it at https://github.com/MISP/MISP!"
msgstr ""
#: Model/Attribute.php:880
msgid "Invalid SSDeep hash. The format has to be blocksize:hash:hash"
msgstr ""
#: Model/Attribute.php:887
msgid "Invalid impfuzzy format. The format has to be imports:hash:hash"
msgstr ""
#: Model/Attribute.php:901
msgid "The input doesn't match the expected filename|sha1 format (expected: filename|40 hexadecimal characters). Keep in mind that MISP currently only supports SHA1 for PEhashes, if you would like to get the support extended to other hash types, make sure to create a github ticket about it at https://github.com/MISP/MISP!"
msgstr ""
#: Model/Attribute.php:919
msgid "Checksum has an invalid length or format (expected: filename|%s hexadecimal characters). Please double check the value or select type \"other\"."
msgstr ""
#: Model/Attribute.php:924
msgid "Invalid composite type. The format has to be %s."
msgid "Checksum has an invalid length or format (expected: filename|at least 35 hexadecimal characters). Please double check the value or select type \"other\"."
msgstr ""
#: Model/Attribute.php:950
msgid "Invalid CIDR notation value found."
msgstr ""
#: Model/Attribute.php:957;1008
msgid "IP address has an invalid format."
msgstr ""
#: Model/Attribute.php:962
msgid "Port numbers have to be positive integers between 1 and 65535."
msgstr ""
#: Model/Attribute.php:991
msgid " name has an invalid format. Please double check the value or select type \"other\"."
msgstr ""
#: Model/Attribute.php:1011
msgid "Domain name has an invalid format."
msgstr ""
#: Model/Attribute.php:1024
msgid "Email address has an invalid format. Please double check the value or select type \"other\"."
msgid "Invalid format. Only values shorter than 256 characters that don't include any forward or backward slashes are allowed."
msgstr ""
#: Model/Attribute.php:1155
msgid "Datetime has to be in the ISO 8601 format."
msgstr ""
#: Model/Attribute.php:1161
msgid "The value has to be a number greater or equal 0."
msgstr ""
#: Model/Attribute.php:1168
msgid "The value has to be a number between 0 and 10."
msgstr ""
#: Model/Attribute.php:1785;1840
msgid "Could not read user."
msgstr ""
#: Model/Attribute.php:2278
msgid "This field is mandatory."
msgstr ""
#: Model/Attribute.php:2609
msgid "Something went wrong. Received a non-numeric event ID while trying to create a zip archive of an uploaded malware sample."
msgstr ""
#: Model/Event.php:4186
msgid "Issues while loading the stix file. "
msgstr ""
#: Model/Event.php:4188
msgid "Issues with the maec library. "
msgstr ""
#: Model/Event.php:4190
msgid "Issues executing the ingestion script or invalid input. "
msgstr ""
#: Model/Event.php:4193
msgid "Please ask your administrator to "
msgstr ""
#: Model/Event.php:4195
msgid "Please "
msgstr ""
#: Model/Event.php:4197
msgid "check whether the dependencies for STIX are met via the diagnostic tool."
msgstr ""
#: Model/Event.php:4236
msgid "#"
msgstr ""
#: Model/Event.php:4244
msgid "%s not set"
msgstr ""
#: Model/Server.php:119
msgid "Certain administrative tasks are exposed to the API, these help with maintaining and configuring MISP in an automated way / via external tools."
msgstr ""
#: Model/Server.php:120
msgid "Administering MISP via the CLI"
msgstr ""
#: Model/Server.php:130
msgid "If you would like to automate tasks such as caching feeds or pulling from server instances, you can do it using the following command line tools. Simply execute the given commands via the command line / create cron jobs easily out of them."
msgstr ""
#: Model/Server.php:131
#: View/Tasks/index.ctp:6
msgid "Automating certain console tasks"
msgstr ""
#: Model/Server.php:141
msgid "The base url of the application (in the format https://www.mymispinstance.com). Several features depend on this setting being correctly set to function."
msgstr ""
#: Model/Server.php:143
msgid "The currenty set baseurl does not match the URL through which you have accessed the page. Disregard this if you are accessing the page via an alternate URL (for example via IP address)."
msgstr ""
#: Model/Server.php:149
msgid "Unless set to true, the instance will only be accessible by site admins."
msgstr ""
#: Model/Server.php:157
msgid "Select the language MISP should use. The default is english."
msgstr ""
#: Model/Server.php:167
msgid "Enable some performance heavy correlations (currently CIDR correlation)"
msgstr ""
#: Model/Server.php:176
msgid "Set the ssdeep score at which to consider two ssdeep hashes as correlating [1-100]"
msgstr ""
#: Model/Server.php:184
msgid "Sets the maximum number of correlations that can be fetched with a single event. For extreme edge cases this can prevent memory issues. The default value is 5k."
msgstr ""
#: Model/Server.php:193
msgid "The message that users will see if the instance is not live."
msgstr ""
#: Model/Server.php:195
msgid "If this is not set the default value will be used."
msgid "This setting is deprecated and can be safely removed."
msgstr ""
#: Model/Server.php:217
msgid "Cached exports can take up a considerable amount of space and can be disabled instance wide using this setting. Disabling the cached exports is not recommended as it's a valuable feature, however, if your server is having free space issues it might make sense to take this step."
msgstr ""
#: Model/Server.php:235
msgid "Footer text prepending the \"Powered by MISP\" text."
msgstr ""
#: Model/Server.php:243
msgid "Footer text following the \"Powered by MISP\" text."
msgstr ""
#: Model/Server.php:283
msgid "If set, this setting allows you to display a logo on the right side of the footer. Upload it as a custom image in the file management tool."
msgstr ""
#: Model/Server.php:291
msgid "If set, this setting allows you to display a logo as the home icon. Upload it as a custom image in the file management tool."
msgstr ""
#: Model/Server.php:299
msgid "If set, the image specified here will replace the main MISP logo on the login screen. Upload it as a custom image in the file management tool."
msgstr ""
#: Model/Server.php:307
msgid "The organisation tag of the hosting organisation. This is used in the e-mail subjects."
msgstr ""
#: Model/Server.php:315
msgid "The hosting organisation of this instance. If this is not selected then replication instances cannot be added."
msgstr ""
#: Model/Server.php:324
msgid "The MISP instance UUID. This UUID is used to identify this instance."
msgstr ""
#: Model/Server.php:326
msgid "No valid UUID set"
msgstr ""
#: Model/Server.php:340
msgid "Setting this setting to 'false' will hide all organisation names / logos."
msgstr ""
#: Model/Server.php:348
msgid "Put the event threat level in the notification E-mail subject."
msgstr ""
#: Model/Server.php:356
msgid "This is the TLP string for e-mails when email_subject_tag is not found."
msgstr ""
#: Model/Server.php:364
msgid "If this tag is set on an event it's value will be sent in the E-mail subject. If the tag is not set the email_subject_TLP_string will be used."
msgstr ""
#: Model/Server.php:372
msgid "Include in name of the email_subject_tag in the subject. When false only the tag value is used."
msgstr ""
#: Model/Server.php:396
msgid "Enables the use of MISP's background processing."
msgstr ""
#: Model/Server.php:404
msgid "Directory where attachments are stored. MISP will NOT migrate the existing data if you change this setting. The only safe way to change this setting is in config.php, when MISP is not running, and after having moved/copied the existing data to the new location. This directory must already exist and be writable and readable by the MISP application."
msgstr ""
#: Model/Server.php:413
msgid "Allow the XML caches to include the encoded attachments."
msgstr ""
#: Model/Server.php:421
msgid "Always download attachments when loaded by a user in a browser"
msgstr ""
#: Model/Server.php:429
msgid "The e-mail address that MISP should use for all notifications"
msgstr ""
#: Model/Server.php:437
msgid "You can disable all e-mailing using this setting. When enabled, no outgoing e-mails will be sent by MISP."
msgstr ""
#: Model/Server.php:446
msgid "The e-mail address that MISP should include as a contact address for the instance's support team."
msgstr ""
#: Model/Server.php:462
msgid "Turn Vulnerability type attributes into links linking to the provided CVE lookup"
msgstr ""
#: Model/Server.php:470
msgid "This setting controls whether notification e-mails will be sent when an event is created via the REST interface. It might be a good idea to disable this setting when first setting up a link to another instance to avoid spamming your users during the initial pull. Quick recap: True = Emails are NOT sent, False = Emails are sent on events published via sync / REST."
msgstr ""
#: Model/Server.php:478
msgid "enabling this flag will allow the event description to be transmitted in the alert e-mail's subject. Be aware that this is not encrypted by GnuPG, so only enable it if you accept that part of the event description will be sent out in clear-text."
msgstr ""
#: Model/Server.php:486
msgid "The default distribution setting for events (0-3)."
msgstr ""
#: Model/Server.php:495
msgid "The default distribution setting for attributes, set it to 'event' if you would like the attributes to default to the event distribution level. (0-3 or \"event\")"
msgstr ""
#: Model/Server.php:504
msgid "The default threat level setting when creating events."
msgstr ""
#: Model/Server.php:513
msgid "Enable the tagging feature of MISP. This is highly recommended."
msgstr ""
#: Model/Server.php:521
msgid "Show the full tag names on the event index."
msgstr ""
#: Model/Server.php:530
msgid "Used on the login page, before the MISP logo"
msgstr ""
#: Model/Server.php:538
msgid "Used on the login page, after the MISP logo"
msgstr ""
#: Model/Server.php:546
msgid "Used on the login page, to the left of the MISP logo, upload it as a custom image in the file management tool."
msgstr ""
#: Model/Server.php:554
msgid "Used on the login page, to the right of the MISP logo, upload it as a custom image in the file management tool."
msgstr ""
#: Model/Server.php:562
msgid "Used in the page title, after the name of the page"
msgstr ""
#: Model/Server.php:570
msgid "Allows users to take ownership of an event uploaded via the \"Add MISP XML\" button. This allows spoofing the creator of a manually imported event, also breaking possibly breaking the original intended releasability. Synchronising with an instance that has a different creator for the same event can lead to unwanted consequences."
msgstr ""
#: Model/Server.php:578
msgid "Choose whether the terms and conditions should be displayed inline (false) or offered as a download (true)"
msgstr ""
#: Model/Server.php:586
msgid "The filename of the terms and conditions file. Make sure that the file is located in your MISP/app/files/terms directory"
msgstr ""
#: Model/Server.php:594
msgid "True enables the alternate org fields for the event index (source org and member org) instead of the traditional way of showing only an org field. This allows users to see if an event was uploaded by a member organisation on their MISP instance, or if it originated on an interconnected instance."
msgstr ""
#: Model/Server.php:602
msgid "True will deny access to unpublished events to users outside the organization of the submitter except site admins."
msgstr ""
#: Model/Server.php:611
msgid "The message sent to the user after account creation (has to be sent manually from the administration interface). Use \\n for line-breaks. The following variables will be automatically replaced in the text: $password = a new temporary password that MISP generates, $username = the user's e-mail address, $misp = the url of this instance, $org = the organisation that the instance belongs to, as set in MISP.org, $contact = the e-mail address used to contact the support team, as set in MISP.contact. For example, \"the password for $username is $password\" would appear to a user with the e-mail address user@misp.org as \"the password for user@misp.org is hNamJae81\"."
msgstr ""
#: Model/Server.php:620
msgid "The message sent to the users when a password reset is triggered. Use \\n for line-breaks. The following variables will be automatically replaced in the text: $password = a new temporary password that MISP generates, $username = the user's e-mail address, $misp = the url of this instance, $contact = the e-mail address used to contact the support team, as set in MISP.contact. For example, \"the password for $username is $password\" would appear to a user with the e-mail address user@misp.org as \"the password for user@misp.org is hNamJae81\"."
msgstr ""
#: Model/Server.php:628
msgid "Since version 2.3.107 you can start blacklisting event UUIDs to prevent them from being pushed to your instance. This functionality will also happen silently whenever an event is deleted, preventing a deleted event from being pushed back from another instance."
msgstr ""
#: Model/Server.php:635
msgid "Blacklisting organisation UUIDs to prevent the creation of any event created by the blacklisted organisation."
msgstr ""
#: Model/Server.php:642
msgid "If enabled, all log entries will include the IP address of the user."
msgstr ""
#: Model/Server.php:651
msgid "If enabled, MISP will log all successful authentications using API keys. The requested URLs are also logged."
msgstr ""
#: Model/Server.php:659
msgid "This feature allows users to create org only events and ask another organisation to take ownership of the event. This allows organisations to remain anonymous by asking a partner to publish an event for them."
msgstr ""
#: Model/Server.php:668
msgid "When enabled, the number of correlations visible to the currently logged in user will be visible on the event index UI. This comes at a performance cost but can be very useful to see correlating events at a glance."
msgstr ""
#: Model/Server.php:677
msgid "When enabled, the number of proposals for the events are shown on the index."
msgstr ""
#: Model/Server.php:686
msgid "When enabled, the aggregate number of attribute sightings within the event becomes visible to the currently logged in user on the event index UI."
msgstr ""
#: Model/Server.php:695
msgid "When enabled, the aggregate number of discussion posts for the event becomes visible to the currently logged in user on the event index UI."
msgstr ""
#: Model/Server.php:704
msgid "When enabled only Org and Site admins can edit a user's profile."
msgstr ""
#: Model/Server.php:714
msgid "Enable this setting to start blocking alert e-mails for events with a certain tag. Define the tag in MISP.block_event_alert_tag."
msgstr ""
#: Model/Server.php:723
msgid "If the MISP.block_event_alert setting is set, alert e-mails for events tagged with the tag defined by this setting will be blocked."
msgstr ""
#: Model/Server.php:732
msgid "Enable this setting to start blocking alert e-mails for old events. The exact timing of what constitutes an old event is defined by MISP.block_old_event_alert_age."
msgstr ""
#: Model/Server.php:741
msgid "If the MISP.block_old_event_alert setting is set, this setting will control how old an event can be for it to be alerted on. The \"Date\" field of the event is used. Expected format: integer, in days"
msgstr ""
#: Model/Server.php:750
msgid "Please indicate the temp directory you wish to use for certain functionalities in MISP. By default this is set to /tmp and will be used among others to store certain temporary files extracted from imports during the import process."
msgstr ""
#: Model/Server.php:759
msgid "If you would like to customise the css, simply drop a css file in the /var/www/MISP/webroot/css directory and enter the name here."
msgstr ""
#: Model/Server.php:768
msgid "Enable this setting to allow blocking attributes from to_ids sensitive exports if a proposal has been made to it to remove the IDS flag or to remove the attribute altogether. This is a powerful tool to deal with false-positives efficiently."
msgstr ""
#: Model/Server.php:777
msgid "Enable this settings if new tags synced / added via incoming events from any source should not be selectable by users by default."
msgstr ""
#: Model/Server.php:786
msgid "*WARNING* This setting will completely disable the correlation on this instance and remove any existing saved correlations. Enabling this will trigger a full recorrelation of all data which is an extremely long and costly procedure. Only enable this if you know what you're doing."
msgstr ""
#: Model/Server.php:796
msgid "*WARNING* This setting will give event creators the possibility to disable the correlation of individual events / attributes that they have created."
msgstr ""
#: Model/Server.php:805
msgid "The host running the redis server to be used for generic MISP tasks such as caching. This is not to be confused by the redis server used by the background processing."
msgstr ""
#: Model/Server.php:813
msgid "The port used by the redis server to be used for generic MISP tasks such as caching. This is not to be confused by the redis server used by the background processing."
msgstr ""
#: Model/Server.php:821
msgid "The database on the redis server to be used for generic MISP tasks. If you run more than one MISP instance, please make sure to use a different database on each instance."
msgstr ""
#: Model/Server.php:829
msgid "The password on the redis server (if any) to be used for generic MISP tasks."
msgstr ""
#: Model/Server.php:838
msgid "Specify which fields to filter on when you search on the event view. Default values are : \"id, uuid, value, comment, type, category, Tag.name\""
msgstr ""
#: Model/Server.php:846
msgid "Only enable this if you have some tools using MISP with extreme high concurency. General performance will be lower as normal as certain transactional queries are avoided in favour of shorter table locks."
msgstr ""
#: Model/Server.php:858
msgid "The location of the GnuPG executable. If you would like to use a different GnuPG executable than /usr/bin/gpg, you can set it here. If the default is fine, just keep the setting suggested by MISP."
msgstr ""
#: Model/Server.php:866
msgid "Allow (false) unencrypted e-mails to be sent to users that don't have a GnuPG key."
msgstr ""
#: Model/Server.php:874
msgid "Allow (false) the body of unencrypted e-mails to contain details about the event."
msgstr ""
#: Model/Server.php:882
msgid "Enable the signing of GnuPG emails. By default, GnuPG emails are signed"
msgstr ""
#: Model/Server.php:890
msgid "The e-mail address that the instance's GnuPG key is tied to."
msgstr ""
#: Model/Server.php:898
msgid "The password (if it is set) of the GnuPG key of the instance."
msgstr ""
#: Model/Server.php:907
msgid "The location of the GnuPG homedir."
msgstr ""
#: Model/Server.php:918
msgid "Enable SMIME encryption. The encryption posture of the GnuPG.onlyencrypted and GnuPG.bodyonlyencrypted settings are inherited if SMIME is enabled."
msgstr ""
#: Model/Server.php:926
msgid "The e-mail address that the instance's SMIME key is tied to."
msgstr ""
#: Model/Server.php:934
msgid "The location of the public half of the signing certificate."
msgstr ""
#: Model/Server.php:942
msgid "The location of the private half of the signing certificate."
msgstr ""
#: Model/Server.php:950
msgid "The password (if it is set) of the SMIME key of the instance."
msgstr ""
#: Model/Server.php:962
msgid "The hostname of an HTTP proxy for outgoing sync requests. Leave empty to not use a proxy."
msgstr ""
#: Model/Server.php:970
msgid "The TCP port for the HTTP proxy."
msgstr ""
#: Model/Server.php:978
msgid "The authentication method for the HTTP proxy. Currently supported are Basic or Digest. Leave empty for no proxy authentication."
msgstr ""
#: Model/Server.php:986
msgid "The authentication username for the HTTP proxy."
msgstr ""
#: Model/Server.php:994
msgid "The authentication password for the HTTP proxy."
msgstr ""
#: Model/Server.php:1005
msgid "The salt used for the hashed passwords. You cannot reset this from the GUI, only manually from the settings.php file. Keep in mind, this will invalidate all passwords in the database."
msgstr ""
#: Model/Server.php:1014
msgid "Enable this setting to pass all audit log entries directly to syslog. Keep in mind, this is verbose and will include user, organisation, event data."
msgstr ""
#: Model/Server.php:1023
msgid "Password length requirement. If it is not set or it is set to 0, then the default value is assumed (12)."
msgstr ""
#: Model/Server.php:1031
msgid "Password complexity requirement. Leave it empty for the default setting (3 out of 4, with either a digit or a special char) or enter your own regex. Keep in mind that the length is checked in another key. Default (simple 3 out of 4 or minimum 16 characters): /^((?=.*\\d)|(?=.*\\W+))(?![\\n])(?=.*[A-Z])(?=.*[a-z]).*$|.{16,}/"
msgstr ""
#: Model/Server.php:1039
msgid "Enabling this setting will require users to submit their current password on any edits to their profile (including a triggered password change). For administrators, the confirmation will be required when changing the profile of any user. Could potentially mitigate an attacker trying to change a compromised user's password in order to establish persistance, however, enabling this feature will be highly annoying to users."
msgstr ""
#: Model/Server.php:1048
msgid "Enabling this setting will sanitise the contents of an attribute on a soft delete"
msgstr ""
#: Model/Server.php:1057
msgid "Enabling this setting will block the organisation index from being visible to anyone besides site administrators on the current instance. Keep in mind that users can still see organisations that produce data via events, proposals, event history log entries, etc."
msgstr ""
#: Model/Server.php:1066
msgid "Allows passing the API key via the named url parameter \"apikey\" - highly recommended not to enable this, but if you have some dodgy legacy tools that cannot pass the authorization header it can work as a workaround. Again, only use this as a last resort."
msgstr ""
#: Model/Server.php:1068
msgid "You have enabled the passing of API keys via URL parameters. This is highly recommended against, do you really want to reveal APIkeys in your logs?..."
msgstr ""
#: Model/Server.php:1078
msgid "The number of tries a user can try to login and fail before the bruteforce protection kicks in."
msgstr ""
#: Model/Server.php:1086
msgid "The duration (in seconds) of how long the user will be locked out when the allowed number of login attempts are exhausted."
msgstr ""
#: Model/Server.php:1097
msgid "Set to true to automatically regenerate sessions after x number of requests. This might lead to the user getting de-authenticated and is frustrating in general, so only enable it if you really need to regenerate sessions. (Not recommended)"
msgstr ""
#: Model/Server.php:1105
msgid "Set to true to check for the user agent string in each request. This can lead to occasional logouts (not recommended)."
msgstr ""
#: Model/Server.php:1113
msgid "The session type used by MISP. The default setting is php, which will use the session settings configured in php.ini for the session data (supported options: php, database). The recommended option is php and setting your PHP up to use redis sessions via your php.ini. Just add 'session.save_handler = redis' and \"session.save_path = 'tcp://localhost:6379'\" (replace the latter with your redis connection) to "
msgstr ""
#: Model/Server.php:1122
msgid "The timeout duration of sessions (in MINUTES)."
msgstr ""
#: Model/Server.php:1130
msgid "The expiration of the cookie (in MINUTES). The session timeout gets refreshed frequently, however the cookies do not. Generally it is recommended to have a much higher cookie_timeout than timeout."
msgstr ""
#: Model/Server.php:1141
msgid "The default policy action for the values added to the RPZ."
msgstr ""
#: Model/Server.php:1150
msgid "The default walled garden used by the RPZ export if the walled garden setting is picked for the export."
msgstr ""
#: Model/Server.php:1158
msgid "The serial in the SOA portion of the zone file. (numeric, best practice is yyyymmddrr where rr is the two digit sub-revision of the file. $date will automatically get converted to the current yyyymmdd, so $date00 is a valid setting)."
msgstr ""
#: Model/Server.php:1166
msgid "The refresh specified in the SOA portion of the zone file. (in seconds, or shorthand duration such as 15m)"
msgstr ""
#: Model/Server.php:1174
msgid "The retry specified in the SOA portion of the zone file. (in seconds, or shorthand duration such as 15m)"
msgstr ""
#: Model/Server.php:1182
msgid "The expiry specified in the SOA portion of the zone file. (in seconds, or shorthand duration such as 15m)"
msgstr ""
#: Model/Server.php:1190
msgid "The minimum TTL specified in the SOA portion of the zone file. (in seconds, or shorthand duration such as 15m)"
msgstr ""
#: Model/Server.php:1198
msgid "The TTL of the zone file. (in seconds, or shorthand duration such as 15m)"
msgstr ""
#: Model/Server.php:1214
msgid "Alternate nameserver"
msgstr ""
#: Model/Server.php:1222
msgid "The e-mail address specified in the SOA portion of the zone file."
msgstr ""
#: Model/Server.php:1230
msgid "Enables or disables the pub/sub feature of MISP. Make sure that you install the requirements for the plugin to work. Refer to the installation instructions for more information."
msgstr ""
#: Model/Server.php:1239
msgid "The port that the pub/sub feature will use."
msgstr ""
#: Model/Server.php:1248
msgid "Location of the Redis db used by MISP and the Python PUB script to queue data to be published."
msgstr ""
#: Model/Server.php:1257
msgid "The port that Redis is listening on."
msgstr ""
#: Model/Server.php:1266
msgid "The password, if set for Redis."
msgstr ""
#: Model/Server.php:1275
msgid "The database to be used for queuing messages for the pub/sub functionality."
msgstr ""
#: Model/Server.php:1284
msgid "The namespace to be used for queuing messages for the pub/sub functionality."
msgstr ""
#: Model/Server.php:1293
msgid "Enable this setting to include the base64 encoded payloads of malware-samples/attachments in the output."
msgstr ""
#: Model/Server.php:1301
msgid "Enables or disables the publishing of any event creations/edits/deletions."
msgstr ""
#: Model/Server.php:1309
msgid "Enables or disables the publishing of any object creations/edits/deletions."
msgstr ""
#: Model/Server.php:1317
msgid "Enables or disables the publishing of any object reference creations/deletions."
msgstr ""
#: Model/Server.php:1325
msgid "Enables or disables the publishing of any attribute creations/edits/soft deletions."
msgstr ""
#: Model/Server.php:1333
msgid "Enables or disables the publishing of any tag creations/edits/deletions as well as tags being attached to / detached from various MISP elements."
msgstr ""
#: Model/Server.php:1341
msgid "Enables or disables the publishing of new sightings to the ZMQ pubsub feed."
msgstr ""
#: Model/Server.php:1349
msgid "Enables or disables the publishing of new/modified users to the ZMQ pubsub feed."
msgstr ""
#: Model/Server.php:1357
msgid "Enables or disables the publishing of new/modified organisations to the ZMQ pubsub feed."
msgstr ""
#: Model/Server.php:1365
msgid "Enables or disables the publishing of log entries to the ZMQ pubsub feed. Keep in mind, this can get pretty verbose depending on your logging settings."
msgstr ""
#: Model/Server.php:1373
msgid "Enabled logging to an ElasticSearch instance"
msgstr ""
#: Model/Server.php:1381
msgid "The URL(s) at which to access ElasticSearch - comma seperate if you want to have more than one."
msgstr ""
#: Model/Server.php:1389
msgid "The index in which to place logs"
msgstr ""
#: Model/Server.php:1397
msgid "This setting defines who will have access to seeing the reported sightings. The default setting is the event owner alone (in addition to everyone seeing their own contribution) with the other options being Sighting reporters (meaning the event owner and anyone that provided sighting data about the event) and Everyone (meaning anyone that has access to seeing the event / attribute)."
msgstr ""
#: Model/Server.php:1406
msgid "Enabling the anonymisation of sightings will simply aggregate all sightings instead of showing the organisations that have reported a sighting. Users will be able to tell the number of sightings their organisation has submitted and the number of sightings for other organisations"
msgstr ""
#: Model/Server.php:1414
msgid "Set the range in which sightings will be taken into account when generating graphs. For example a sighting with a sighted_date of 7 years ago might not be relevant anymore. Setting given in number of days, default is 365 days"
msgstr ""
#: Model/Server.php:1422
msgid "Enable this functionality if you would like to handle the authentication via an external tool and authenticate with MISP using a custom header."
msgstr ""
#: Model/Server.php:1432
msgid "Set the header that MISP should look for here. If left empty it will default to the Authorization header."
msgstr ""
#: Model/Server.php:1441
msgid "Use a header namespace for the auth header - default setting is enabled"
msgstr ""
#: Model/Server.php:1450
msgid "The default header namespace for the auth header - default setting is HTTP_"
msgstr ""
#: Model/Server.php:1459
msgid "If this setting is enabled then the only way to authenticate will be using the custom header. Altnertatively you can run in mixed mode that will log users in via the header if found, otherwise users will be redirected to the normal login page."
msgstr ""
#: Model/Server.php:1468
msgid "If you are using an external tool to authenticate with MISP and would like to only allow the tool's url as a valid point of entry then set this field. "
msgstr ""
#: Model/Server.php:1477
msgid "The name of the authentication method, this is cosmetic only and will be shown on the user creation page and logs."
msgstr ""
#: Model/Server.php:1486
msgid "Disable the logout button for users authenticate with the external auth mechanism."
msgstr ""
#: Model/Server.php:1494
msgid "Enable/disable the enrichment services"
msgstr ""
#: Model/Server.php:1502
msgid "Set a timeout for the enrichment services"
msgstr ""
#: Model/Server.php:1510;1622
msgid "Enable/disable the import services"
msgstr ""
#: Model/Server.php:1518;1639
msgid "Set a timeout for the import services"
msgstr ""
#: Model/Server.php:1526
msgid "The url used to access the import services. By default, it is accessible at http://127.0.0.1:6666"
msgstr ""
#: Model/Server.php:1534
msgid "The port used to access the import services. By default, it is accessible at 127.0.0.1:6666"
msgstr ""
#: Model/Server.php:1542
msgid "The url used to access the export services. By default, it is accessible at http://127.0.0.1:6666"
msgstr ""
#: Model/Server.php:1550
msgid "The port used to access the export services. By default, it is accessible at 127.0.0.1:6666"
msgstr ""
#: Model/Server.php:1558
msgid "Enable/disable the export services"
msgstr ""
#: Model/Server.php:1566
msgid "Set a timeout for the export services"
msgstr ""
#: Model/Server.php:1574
msgid "Enable/disable the hover over information retrieved from the enrichment modules"
msgstr ""
#: Model/Server.php:1582
msgid "Set a timeout for the hover services"
msgstr ""
#: Model/Server.php:1590
msgid "The url used to access the enrichment services. By default, it is accessible at http://127.0.0.1:6666"
msgstr ""
#: Model/Server.php:1598
msgid "The port used to access the enrichment services. By default, it is accessible at 127.0.0.1:6666"
msgstr ""
#: Model/Server.php:1606
msgid "The url used to access Cortex. By default, it is accessible at http://cortex-url"
msgstr ""
#: Model/Server.php:1614
msgid "The port used to access Cortex. By default, this is port 9000"
msgstr ""
#: Model/Server.php:1630
msgid "Set an authentication key to be passed to Cortex"
msgstr ""
#: Model/Server.php:1647
msgid "Set to false to disable SSL verification. This is not recommended."
msgstr ""
#: Model/Server.php:1656
msgid "Set to false if you wish to ignore hostname match errors when validating certificates."
msgstr ""
#: Model/Server.php:1665
msgid "Set to true to enable self-signed certificates to be accepted. This requires Cortex_ssl_verify_peer to be enabled."
msgstr ""
#: Model/Server.php:1674
msgid "Set to the absolute path of the Certificate Authority file that you wish to use for verifying SSL certificates."
msgstr ""
#: Model/Server.php:1683
msgid "Provide your custom authentication users with an external URL to the authentication system to reset their passwords."
msgstr ""
#: Model/Server.php:1692
msgid "Provide a custom logout URL for your users that will log them out using the authentication system you use."
msgstr ""
#: Model/Server.php:1702
msgid "The debug level of the instance, always use 0 for production instances."
msgstr ""
#: Model/Server.php:1711
msgid "The debug level of the instance for site admins. This feature allows site admins to run debug mode on a live instance without exposing it to other users. The most verbose option of debug and site_admin_debug is used for site admins."
msgstr ""
#: Model/Server.php:2342;2377
msgid "Enable or disable the %s module."
msgstr ""
#: Model/Server.php:2345;2380
msgid "Restrict the %s module to the given organisation."
msgstr ""
#: Model/Server.php:2353;2388
msgid "Set this required module specific setting."
msgstr ""
#: Model/Server.php:2458
msgid "Value not set."
msgstr ""
#: Model/Server.php:2911
msgid "Organisation logos"
msgstr ""
#: Model/Server.php:2912
msgid "The logo used by an organisation on the event index, event view, discussions, proposals, etc. Make sure that the filename is in the org.png format, where org is the case-sensitive organisation name."
msgstr ""
#: Model/Server.php:2914
msgid "48x48 pixel .png files"
msgstr ""
#: Model/Server.php:2917;2932
msgid "Filename must be in the following format: *.png"
msgstr ""
#: Model/Server.php:2921
msgid "Additional image files"
msgstr ""
#: Model/Server.php:2922
msgid "Image files uploaded into this directory can be used for various purposes, such as for the login page logos"
msgstr ""
#: Model/Server.php:2929
msgid "text/html if served inline, anything that conveys the terms of use if served as download"
msgid "This is a list of events that match the given search criteria sorted according to the percentage of matched attributes that are marked as IDS signatures (blue = IDS matches, red = non IDS matches)."
msgid "Choose a category and a type, then paste a list of IOCs that match the selection into the field below. This will delete all of the attributes not found in the new inserted list, whilst creating the attributes that are in the new list but don't exist as attributes. Found matches will be left untouched."
msgid "Warning: You are about to share data that is of a classified nature (Attribution / targeting data). Make sure that you are authorised to share this."
msgstr ""
#: View/Attributes/attribute_replace.ctp:38
msgid "Replace attributes"
msgstr ""
#: View/Attributes/attribute_replace.ctp:38
msgid "Replaceattributes"
msgstr ""
#: View/Attributes/check_composites.ctp:2
msgid "Failed Composites"
msgstr ""
#: View/Attributes/check_composites.ctp:4
msgid "No Failed Composites"
msgstr ""
#: View/Attributes/edit.ctp:16
#: View/Pages/doc/using_the_system.ctp:368
msgid "disabled"
msgstr ""
#: View/Attributes/edit.ctp:64
#: View/ShadowAttributes/add.ctp:55
#: View/ShadowAttributes/edit.ctp:45;54
msgid "Warning: You are about to share data that is of a sensitive nature (Attribution / targeting data). Make sure that you are authorised to share this."
msgid "You can search for attributes based on contained expression within the value, event ID, submitting organisation, category and type. <br />For the value, event ID and organisation, you can enter several search terms by entering each term as a new line. To exclude things from a result, use the NOT operator (!) in front of the term."
msgstr ""
#: View/Attributes/search.ctp:7
msgid "For string searches (such as searching for an expression, tags, etc) - lookups are simple string matches. If you want a substring match encapsulate the lookup string between \"%\" characters."
msgstr ""
#: View/Attributes/search.ctp:10
msgid "Containing the following expressions"
msgstr ""
#: View/Attributes/search.ctp:11
msgid "Being an attribute matching the following tags"
msgstr ""
#: View/Attributes/search.ctp:12
msgid "Being attributes of the following event IDs, event UUIDs or attribute UUIDs"
msgstr ""
#: View/Attributes/search.ctp:13
msgid "Being an attribute of an event matching the following tags"
msgid "Are you sure you want to hard-delete Attribute #%s? The Attribute will be permanently deleted and unrecoverable. Also, this will prevent the deletion to be propagated to other instances."
msgid "Are you sure you want to soft-delete Attribute #%s? The Attribute will only be soft deleted, meaning that it is not completely purged. Click on Include deleted attributes and delete the soft deleted attribute if you want to permanently remove it."
msgid "Re-enable the correlation for this attribute."
msgstr ""
#: View/Attributes/ajax/toggle_correlation.ctp:13
msgid "This will remove all correlations that already exist for this attribute and prevents any attributes to be related as long as this setting is disabled. Make sure you understand the downsides of disabling correlations."
msgid "Attribute warning: This event doesn't have any attributes visible to you. Either the owner of the event decided to have\n"
"a specific distribution scheme per attribute and wanted to still distribute the event alone either for notification or potential contribution with attributes without such restriction. Or the owner forgot to add the\n"
"attributes or the appropriate distribution level. If you think there is a mistake or you can contribute attributes based on the event meta-information, feel free to make a proposal"
msgstr ""
#: View/Elements/eventattribute.ctp:242
msgid "Attribute warning: This event doesn't contain any attribute. It's strongly advised to populate the event with attributes (indicators, observables or information) to provide a meaningful event"
msgid "Incorrect database encoding setting: Your database connection is currently NOT set to UTF-8. Please make sure to uncomment the 'encoding' => 'utf8' line in "
msgid "Every version of MISP includes a json file with the current version. This is checked against the latest tag on github, if there is a version mismatch the tool will warn you about it. Make sure that you update MISP regularly."
msgid "The following directories and files have to be writeable for MISP to function properly. Make sure that the apache user has write privileges for the directories below."
msgid "The following settings might have a negative impact on certain functionalities of MISP with their current and recommended minimum settings. You can adjust these in your php.ini. Keep in mind that the recommendations are not requirements, just recommendations. Depending on usage you might want to go beyond the recommended values."
msgid "Mitre's STIX and Cybox python libraries have to be installed in order for MISP's STIX export to work. Make sure that you install them (as described in the MISP installation instructions) if you receive an error below."
msgid "If you run into any issues here, make sure that both STIX and CyBox are installed as described in the INSTALL.txt file. The required versions are"
msgid "This tool checks how large your database's session table is. <br />Sessions in CakePHP rely on PHP's garbage collection for clean-up and in certain distributions this can be disabled by default resulting in an ever growing cake session table. <br />If you are affected by this, just click the clean session table button below."
msgid "Prior to 2.4.89, due to a bug a situation could occur where objects got overwritten on a sync pull. This tool allows you to inspect whether you are affected and if yes, remedy the issue."
msgid "In some rare cases attributes can remain in the database after an event is deleted becoming orphaned attributes. This means that they do not belong to any event, which can cause issues with the correlation engine (known cases include event deletion directly in the database without cleaning up the attributes and situations involving a race condition with an event deletion happening before all attributes are synchronised over)."
msgid "Run a full validation of all GnuPG keys within this instance's userbase. The script will try to identify possible issues with each key and report back on the results."
msgid "If you run into an issue with an infinite upgrade loop (when upgrading from version ~2.4.50) that ends up filling your database with upgrade script log messages, run the following script."
msgid "Click the following button to go to the legacy administrative tools page. There should in general be no need to do this unless you are upgrading a very old MISP instance (<2.4), all updates are done automatically with more current versions."
msgid "MISP cannot access your /proc directory to check the status of the worker processes, which means that dead workers will not be detected by the diagnostic tool. If you would like to regain this functionality, make sure that the open_basedir directive is not set, or that /proc is included in it."
msgstr ""
#: View/Elements/healthElements/workers.ctp:10
msgid "Issues prevent jobs from being processed. Please resolve them below."
msgstr ""
#: View/Elements/healthElements/workers.ctp:15
msgid "Worker started with the correct user, but the current status is unknown."
msgstr ""
#: View/Elements/healthElements/workers.ctp:24
msgid "There are issues with the worker(s), but at least one healthy worker is monitoring the queue."
msgid "You have tripped the cross-site request forgery protection of MISP"
msgstr ""
#: View/Errors/error400.ctp:35
msgid "CSRF error"
msgstr ""
#: View/Errors/error400.ctp:36
msgid "This happens usually when you try to resubmit the same form with invalidated CSRF tokens or you had a form open too long and the CSRF tokens simply expired. Just go back to the previous page and refresh the form (by reloading the same url) so that the tokens get refreshed."
msgstr ""
#: View/Errors/error400.ctp:39
msgid "Alternatively, click <a href=\"%s\">here</a> to continue to the start page."
msgstr ""
#: View/Errors/error403.ctp:4
msgid "%s"
msgstr ""
#: View/Errors/missing_connection.ctp:1
#: View/Errors/missing_datasource_config.ctp:1
msgid "Missing Database Connection"
msgstr ""
#: View/Errors/pdo_error.ctp:1
msgid "PDO error"
msgstr ""
#: View/EventBlacklists/add.ctp:4
#: View/EventBlacklists/edit.ctp:4
#: View/OrgBlacklists/edit.ctp:4
msgid "Add Event Blacklist Entries"
msgstr ""
#: View/EventBlacklists/add.ctp:5
#: View/EventBlacklists/edit.ctp:5
#: View/OrgBlacklists/edit.ctp:5
msgid "Simply paste a list of all the event UUIDs that you wish to block from being entered."
msgstr ""
#: View/EventBlacklists/add.ctp:11
#: View/OrgBlacklists/add.ctp:11
msgid "Enter a single or a list of UUIDs"
msgstr ""
#: View/EventBlacklists/add.ctp:17
msgid "(Optional) The organisation that the event is associated with"
msgstr ""
#: View/EventBlacklists/add.ctp:24
msgid "(Optional) the event info of the event that you would like to block. It's best to leave this empty if you are adding a list of UUIDs."
msgstr ""
#: View/EventBlacklists/add.ctp:30
#: View/OrgBlacklists/add.ctp:23
msgid "(Optional) Any comments you would like to add regarding this (or these) entries."
msgstr ""
#: View/EventBlacklists/edit.ctp:10
#: View/OrgBlacklists/edit.ctp:10
msgid "Creating organisation"
msgstr ""
#: View/EventBlacklists/index.ctp:2
msgid "Event Blacklists"
msgstr ""
#: View/EventBlacklists/index.ctp:39
msgid "Are you sure you want to delete the blacklist entry for the event UUID %s?"
msgid "Warning: This will change the creator organisation of the event, tampering with the event's ownership and releasability and can lead to unexpected behaviour when synchronising the event with instances that have another creator for the same event.)"
msgid "Automation functionality is designed to automatically generate signatures for intrusion detection systems. To enable signature generation for a given attribute, Signature field of this attribute must be set to Yes.\n"
"\tNote that not all attribute types are applicable for signature generation, currently we only support NIDS signature generation for IP, domains, host names, user agents etc., and hash list generation for MD5/SHA1 values of file artefacts. Support for more attribute types is planned.\n"
"\tTo to make this functionality available for automated tools an authentication key is used. This makes it easier for your tools to access the data without further form-based-authentication."
msgid "Since version 2.2 the usage of the authentication key in the URL is deprecated. Instead, pass the auth key in an Authorization header in the request. The legacy option of having the auth key in the URL is temporarily still supported but not recommended."
msgstr ""
#: View/Events/automation.ctp:11
msgid "Please use the use the following header"
msgstr ""
#: View/Events/automation.ctp:12
msgid "Authorization"
msgstr ""
#: View/Events/automation.ctp:13
msgid "XML Export"
msgstr ""
#: View/Events/automation.ctp:14
msgid "An automatic export of all events and attributes <small>(except file attachments)</small> is available under a custom XML format."
msgstr ""
#: View/Events/automation.ctp:15;47;76
msgid "You can configure your tools to automatically download the following file"
msgstr ""
#: View/Events/automation.ctp:17
msgid "If you only want to fetch a specific event append the eventid number"
"\tYou can also chain several tag commands together with the '&&' operator. Please be aware the colons (:) cannot be used in the tag search.\n"
"\tUse semicolons instead (the search will automatically search for colons instead). For example, to include tag1 and tag2 but exclude tag3 you would use"
msgid "Events published within the last x amount of time, where x can be defined in days, hours, minutes (for example 5d or 12h or 30m). This filter will use the published timestamp of the event."
msgid "The keywords false or null should be used for optional empty parameters in the URL."
msgstr ""
#: View/Events/automation.ctp:43
msgid "Also check out the %s to read about the REST API."
msgstr ""
#: View/Events/automation.ctp:45
msgid "CSV Export"
msgstr ""
#: View/Events/automation.ctp:46
msgid "An automatic export of attributes is available as CSV. Only attributes that are flagged \"to_ids\" will get exported."
msgstr ""
#: View/Events/automation.ctp:49
msgid "You can specify additional flags for CSV exports as follows"
msgstr ""
#: View/Events/automation.ctp:53
msgid "Setting this flag to true will include attributes that are not marked \"to_ids\"."
msgstr ""
#: View/Events/automation.ctp:58
msgid "For example, to only download a csv generated of the \"domain\" type and the \"Network activity\" category attributes all events except for the one and further restricting it to events that are tagged \"tag1\" or \"tag2\" but not \"tag3\", only allowing attributes that are IDS flagged use the following syntax"
msgid "The attribute type, any valid MISP attribute type is accepted."
msgstr ""
#: View/Events/automation.ctp:63
msgid "Include the event data with each attribute."
msgstr ""
#: View/Events/automation.ctp:66
msgid "Events published within the last x amount of time, where x can be defined in days, hours, minutes (for example 5d or 12h or 30m).This filter will use the published timestamp of the event."
msgstr ""
#: View/Events/automation.ctp:67
msgid "The CSV created when this setting is set to true will not contain the header row.\n"
msgid "To export the attributes of all events that are of the type \"domain\", use the following syntax"
msgstr ""
#: View/Events/automation.ctp:74
msgid "NIDS rules export"
msgstr ""
#: View/Events/automation.ctp:75
msgid "Automatic export of all network related attributes is available under the Snort rule format. Only <em>published</em> events and attributes marked as <em>IDS Signature</em> are exported."
msgid "Some commented out explanation framing the data. The reason to disable this would be if you would like to concatenate a list of exports from various select events in order to avoid unnecessary duplication of the comments."
msgid "Events published within the last x amount of time, where x can be defined in days, hours, minutes (for example 6d or 12h or 30m). This filter will use the published timestamp of the event."
msgid "An example for a suricata export for all events excluding those tagged tag1, without all of the commented information at the start of the file would look like this:"
msgid "Automatic export of MD5/SHA1 checksums contained in file-related attributes. This list can be used to feed forensic software when searching for suspicious files. Only <em>published</em> events and attributes marked as <em>IDS Signature</em> are exported."
msgid "You can export MISP events in Mitre's STIX format (to read more about STIX, click <a href=\"https://stix.mitre.org/\">here</a>). The STIX XML export is currently very slow and can lead to timeouts with larger events or collections of events. The JSON return format does not suffer from this issue. Usage"
msgid "Search parameters can be passed to the function via URL parameters or by POSTing an XML or JSON object (depending on the return type). The following parameters can be passed to the STIX export tool: <code>id</code>, <code>withAttachments</code>, <code>tags</code>. Both <code>id</code> and <code>tags</code> can use the <code>&&</code> (and) and <code>!</code> (not) operators to build queries. Using the URL parameters, the syntax is as follows"
msgid "For example, to retrieve all events tagged \"APT1\" but excluding events tagged \"OSINT\" and excluding events #51 and #62 without any attachments"
msgid "The same search could be accomplished using the following POSTed XML object (note that ampersands need to be escaped, or alternatively separate id and tag elements can be used)"
msgid ">You can export RPZ zone files for DNS level firewalling by using the RPZ export functionality of MISP. The file generated will include all of the IDS flagged domain, hostname and IP-src/IP-dst attribute values that you have access to."
"\t You can also chain several tag commands together with the '&&' operator. Please be aware the colons (:) cannot be used in the tag search when passed through the url.\n"
msgid "MISP will inject header values into the zone file as well as define the action taken for each of the values that can all be overriden. By default these values are either the default values shipped with the application, or ones that are overriden by your site administrator. The values are as follows"
msgid ">An export of all attributes of a specific type to a plain text file. By default only published and IDS flagged attributes are exported."
msgstr ""
#: View/Events/automation.ctp:194
msgid "To restrict the results by tags, use the usual syntax. Please be aware the colons (:) cannot be used in the tag search. Use semicolons instead (the search will automatically search for colons instead). To get ip-src values from events tagged tag1 but not tag2 use"
msgid "As of version 2.3.38, it is possible to restrict the text exports on two additional flags. The first allows the user to restrict based on event ID, whilst the second is a boolean switch allowing non IDS flagged attributes to be exported. Additionally, choosing \"all\" in the type field will return all eligible attributes."
msgid "You can also chain several tag commands together with the '&&' operator. Please be aware the colons (:) cannot be used in the tag search.\n"
"\tUse semicolons instead (the search will automatically search for colons instead). For example, to include tag1 and tag2 but exclude tag3 you would use"
msgid "An export of all attributes of a specific bro type to a formatted plain text file. By default only published and IDS flagged attributes are exported."
msgid "To restrict the results by tags, use the usual syntax. Please be aware the colons (:) cannot be used in the tag search. Use semicolons instead (the search will automatically search for colons instead). To get ip values from events tagged tag1 but not tag2 use"
msgid "Alternatively, it is also possible to pass the filters via the parameters in the URL, though it is highly advised to use POST requests with JSON objects instead. The format is as described below"
"\tYou can also chain several tag commands together with the '&&' operator. Please be aware the colons (:) cannot be used in the tag search.\n"
"\tUse semicolons instead (the search will automatically search for colons instead)."
msgid "Enabling this (by passing \"1\" as the argument) will make the search ignore all of the other arguments, except for the auth key and value. MISP will return an xml / json (depending on the header sent) of all events that have a sub-string match on value in the event info, event orgc, or any of the attribute value1 / value2 fields, or in the attribute comment."
msgid "Restrict the results by the timestamp (last edit). Any event with a timestamp newer than the given timestamp will be returned. In case you are dealing with /attributes as scope, the attribute's timestamp will be used for the lookup."
msgid "For example, to find any event with the term \"red october\" mentioned, use the following syntax (the example is shown as a POST request instead of a GET, which is highly recommended. GET requests are problematic and deprecated.)"
msgid "By default (0) all attributes are returned that match the other filter parameters, irregardless of their to_ids setting. To restrict the returned data set to to_ids only attributes set this parameter to 1. You can only use the special \"exclude\" setting to only return attributes that have the to_ids flag disabled."
msgstr ""
#: View/Events/automation.ctp:315
msgid "If this parameter is set to 1, it will return soft-deleted attributes along with active ones. By using \"only\" as a parameter it will limit the returned data set to soft-deleted data only."
msgstr ""
#: View/Events/automation.ctp:316
msgid "Instead of just including the event ID, also include the event UUID in each of the attributes."
msgstr ""
#: View/Events/automation.ctp:317
msgid "Only return attributes from events that have received a modification after the given timestamp."
msgid "The keywords false or null should be used for optional empty parameters in the URL. Keep in mind, this is only needed if you use the deprecated URL parameters."
msgid "value, type, category and org are optional. It is possible to search for several terms in each category by joining them with the '&&' operator. It is also possible to negate a term with the '!' operator. Please be aware the colons (:) cannot be used in the tag search. Use semicolons instead (the search will automatically search for colons instead).\n"
"\tFor example, in order to search for all attributes created by your organisation that contain 192.168 or 127.0 but not 0.1 and are of the type ip-src, excluding the events that were tagged tag1 use the following syntax"
msgid "You can also use search for IP addresses using CIDR. Make sure that you use '|' (pipe) instead of '/' (slashes). Please be aware the colons (:) cannot be used in the tag search. Use semicolons instead (the search will automatically search for colons instead). See below for an example"
msgid "You can also download samples by knowing its MD5 hash. Simply pass the hash along as a JSON/XML object or in the URL (with the URL having overruling the passed objects) to receive a JSON/XML object back with the zipped sample base64 encoded along with some contextual information."
msgid "You can also use this API to get all samples from events that contain the passed hash. For this functionality, just pass the \"allSamples\" flag along. Note that if you are getting all samples from matching events, you can use all supported hash types (%s) for the lookup.</p>"
msgid "You can also get all the samples from an event with a given event ID, by passing along the eventID parameter. Make sure that either an event ID or a hash is passed along, otherwise an error message will be returned. Also, if no hash is set, the allSamples flag will get set automatically."
msgid "This API will allow you to populate an event that you have modify rights to with malware samples (and all related hashes). Alternatively, if you do not supply an event ID, it will create a new event for you."
msgid "The files have to be base64 encoded and POSTed as explained below. All samples will be zipped and password protected (with the password being \"infected\"). The hashes of the original file will be captured as additional attributes."
msgid "The Event's ID is optional. It can be either supplied via the URL or the POSTed object, but the URL has priority if both are provided. Not supplying an event ID will cause MISP to create a single new event for all of the POSTed malware samples. You can define the default settings for the event, otherwise a set of default settings will be used."
msgid "The category that will be assigned to the uploaded samples. Valid options are: Payload delivery, Artefacts dropped, Payload Installation, External Analysis."
msgid "Used to populate the event info field if no event ID supplied. Alternatively, if not set, MISP will simply generate a message showing that it's a malware sample collection generated on the given day."
msgid "As described in the REST section, it is possible to retrieve a list of events along with their metadata by sending a GET request to the /events API. However, this API in particular is a bit more versatile. You can pass search parameters along to search among the events on various fields and retrieve a list of matching events (along with their metadata). Use the following URL"
msgid "The above would return any event that is published, not restricted to your organisation only that has the term \"Locky\" in its event description. You can use exclamation marks to negate a value wherever appropriate."
msgid "Filters on the date, anything older than the given date in YYYY-MM-DD format is taken - non-negatable"
msgstr ""
#: View/Events/contact.ctp:8
msgid "Contact organization reporting event "
msgstr ""
#: View/Events/contact.ctp:9
msgid "You are about to contact the organization that reported event %s.<br/>\n"
"\t\t\t\tFeel free to add a custom message that will be sent to the reporting organization. <br/>\n"
"\t\t\t\tYour email address and details about the event will be added automagically to the message."
msgstr ""
#: View/Events/contact.ctp:21
msgid "Submit only to the person that created the event"
msgstr ""
#: View/Events/export.ctp:3
#: View/Events/export_alternate.ctp:3
msgid "Export functionality is designed to automatically generate signatures for intrusion detection systems. To enable signature generation for a given attribute, Signature field of this attribute must be set to Yes.\n"
"\t\tNote that not all attribute types are applicable for signature generation, currently we only support NIDS signature generation for IP, domains, host names, user agents etc., and hash list generation for MD5/SHA1 values of file artifacts. Support for more attribute types is planned."
msgstr ""
#: View/Events/export.ctp:6
#: View/Events/export_alternate.ctp:6
msgid "Simply click on any of the following buttons to download the appropriate data."
msgid "Warning, the background worker is not responding!"
msgstr ""
#: View/Events/export.ctp:172
msgid "0 seconds ago"
msgstr ""
#: View/Events/export_alternate.ctp:10
msgid "Download all as XML"
msgstr ""
#: View/Events/export_alternate.ctp:12
msgid "Click this to download all events and attributes that you have access to <small>(except file attachments)</small> in a custom XML format."
msgstr ""
#: View/Events/export_alternate.ctp:17
msgid "Download all signatures as CSV"
msgstr ""
#: View/Events/export_alternate.ctp:19
msgid "Click this to download all attributes that are indicators and that you have access to <small>(except file attachments)</small> in CSV format."
msgstr ""
#: View/Events/export_alternate.ctp:24
msgid "Download all as CSV"
msgstr ""
#: View/Events/export_alternate.ctp:26
msgid "Click this to download all attributes that you have access to <small>(except file attachments)</small> in CSV format."
msgstr ""
#: View/Events/export_alternate.ctp:31
msgid "Download Suricata signatures"
msgstr ""
#: View/Events/export_alternate.ctp:32
msgid "Download Snort signatures"
msgstr ""
#: View/Events/export_alternate.ctp:34
msgid "Click these to download all network related attributes that you\n"
"\t\t\t\t\t\thave access to under the Suricata or Snort rule format. Only <em>published</em>\n"
"\t\t\t\t\t\tevents and attributes marked as <em>IDS Signature</em> are exported.\n"
"\t\t\t\t\t\tAdministration is able to maintain a whitelist containing host,\n"
"\t\t\t\t\t\tdomain name and IP numbers to exclude from the NIDS export."
msgstr ""
#: View/Events/export_alternate.ctp:43
msgid "Download Bro signatures"
msgstr ""
#: View/Events/export_alternate.ctp:45
msgid "Click these to download all network related attributes that you\n"
"\t\t\t\thave access to under the Bro rule format. Only <em>published</em>\n"
"\t\t\t\tevents and attributes marked as <em>IDS Signature</em> are exported.\n"
"\t\t\t\tAdministration is able to maintain a whitelist containing host,\n"
"\t\t\t\tdomain name and IP numbers to exclude from the NIDS export."
msgstr ""
#: View/Events/export_alternate.ctp:54
msgid "Download RPZ Zone File"
msgstr ""
#: View/Events/export_alternate.ctp:56
msgid "Click this to download an RPZ Zone file generated from all ip-src/ip-dst, hostname, domain attributes. This can be useful for DNS level firewalling. Only published events and attributes marked as IDS Signature are exported."
msgstr ""
#: View/Events/export_alternate.ctp:61
msgid "Download all MD5 hashes"
msgstr ""
#: View/Events/export_alternate.ctp:62
msgid "Download all SHA1 hashes"
msgstr ""
#: View/Events/export_alternate.ctp:64
msgid "Click on one of these two buttons to download all MD5 or SHA1\n"
"\t\t\t\t\t\tchecksums contained in file-related attributes. This list can be\n"
"\t\t\t\t\t\tused to feed forensic software when searching for susipicious files.\n"
"\t\t\t\t\t\tOnly <em>published</em> events and attributes marked as <em>IDS\n"
"\t\t\t\t\t\t\tSignature</em> are exported."
msgstr ""
#: View/Events/export_alternate.ctp:72
msgid "Click on one of these buttons to download all the attributes with the matching type. This list can be used to feed forensic software when searching for susipicious files. Only <em>published</em> events and attributes marked as <em>IDS Signature</em> are exported."
msgid "Below you can see the %s that are to be created. Make sure that the categories and the types are correct, often several options will be offered based on an inconclusive automatic resolution."
msgid "Warning: You are missing warninglist(s) that are used to recognise TLDs. Make sure your MISP has the warninglist submodule enabled and updated or else this tool might end up missing valid domains/hostnames/urls. The missing lists are: %s"
msgid "correlations with data contained within the various feeds, however, due to the large number of attributes the actual feed correlations are not shown. Click (<a href=\"%s\\/overrideLimit:1\">here</a> to refresh the page with the feed data loaded."
msgid "Re-enable the correlation for this event. This will automatically re-correlate all contained attributes."
msgstr ""
#: View/Events/ajax/toggle_correlation.ctp:13
msgid "This will remove all correlations that already exist for the event and prevent any events to be related via correlations as long as this setting is disabled. Make sure you understand the downsides of disabling correlations."
msgid "Add a regex pattern for detecting iocs that should be skipped (this can be useful to exclude any references to the actual report / feed for example)"
msgid "Are you sure you want to purge all completed job entries? Job entries are considered as log entries and have no impact on actual job execution."
msgstr ""
#: View/Jobs/index.ctp:18
msgid "Are you sure you want to purge all job entries? Job entries are considered as log entries and have no impact on actual job execution."
msgid "No error data found. Generally job error data is purged from Redis after 24 hours, however, you can still view the errors in the log files in \"/app/tmp/logs\"."
msgid "Due to a bug prior to version 2.4.89, a condition could cause objects to be overwritten on a pull, leading to orphaned object attributes. This script reconstructs the missing objects if any exist."
msgstr ""
#: View/Objects/orphaned_object_diagnostics.ctp:6
msgid " Please create a backup of your mysql database before executing the script."
msgstr ""
#: View/Objects/orphaned_object_diagnostics.ctp:9
msgid "No unmapped data found, everything is working as expected."
msgid "If the organisation should have access to this instance, make sure that the Local organisation setting is checked. <br />If you would only like to add a known external organisation for inclusion in sharing groups, uncheck the Local organisation setting."
msgid "This will remove the selected organisation and hand over all objects belonging to it to the target organisation. This process is irreversible. Are you sure you want to proceed?"
msgstr ""
#: View/Organisations/ajax/merge.ctp:6
msgid "Warning: Merging an organisation into another will be transfer all users and data belonging to the organisation to another."
msgid "Mark organisation as sharing group extender"
msgstr ""
#: View/Pages/administration.ctp:10
msgid "Administrative actions"
msgstr ""
#: View/Pages/administration.ctp:14
msgid "Reset the attribute counts"
msgstr ""
#: View/Pages/administration.ctp:14
msgid "Events need to have no validation issues"
msgstr ""
#: View/Pages/administration.ctp:18
msgid "Verify Certificates"
msgstr ""
#: View/Pages/administration.ctp:18
msgid "Check whether every user's certificate is usable"
msgstr ""
#: View/Pages/administration.ctp:19
msgid "Extend Organization length"
msgstr ""
#: View/Pages/administration.ctp:19
msgid "Hotfix 2.3.57: Increase the max length of the organization field when adding a new server connection."
msgstr ""
#: View/Pages/administration.ctp:20
msgid "Hotfix 2.3.78: Some of the log fields that were varchar(255) ended up truncating the data. This function will change them to \"text\""
msgstr ""
#: View/Pages/administration.ctp:21
msgid "Fix duplicate UUIDs"
msgstr ""
#: View/Pages/administration.ctp:21
msgid "Hotfix 2.3.107: it was previously possible to get duplicate attribute UUIDs in the database, this script will remove all duplicates and ensure that duplicates will not be entered into the database in the future."
msgstr ""
#: View/Pages/administration.ctp:22
msgid "Hotfix 2.3.115: In some rare situations it could occur that a duplicate of an event was created on an instance, with the exact same uuid. This action will remove any such duplicates and make sure that this cannot happen again."
msgstr ""
#: View/Pages/administration.ctp:23
msgid "In some rare occasions it can happen that you end up with some attributes in your database that do not belong to an event - for example during a race condition between an event insert and a delete. This tool will collect and delete any such orphaned attributes. If you ever run into an issue where you cannot add an attribute with a specific valid value, this is probably the reason."
msgstr ""
#: View/Pages/administration.ctp:24
msgid "Hotfix 2.3.160: Prior to this version it was possible for a user/admin with Regex permission to create a malicious regular expression that could be used to execute arbitrary code. Since this version it is no longer possible to input such expressions, but already existing malicious entries still have to be cleaned using this tool."
msgstr ""
#: View/Pages/administration.ctp:25
msgid "Hotfix 2.3.173: Sanitised URLs can cause issues with the NIDS exports and as of this version attributes will be modified on entry to correct this. To correct existing entries, run this script."
msgstr ""
#: View/Pages/administration.ctp:26
msgid "Index tables"
msgstr ""
#: View/Pages/administration.ctp:26
msgid "This script will create indeces for all of the tables in MISP (other than primary keys)"
msgstr ""
#: View/Pages/administration.ctp:27
msgid "Fix non-empty sharing group IDs"
msgstr ""
#: View/Pages/administration.ctp:27
msgid "This script will change the sharing_group_id to 0 in all non sharing group setting events and attributes)"
msgstr ""
#: View/Pages/administration.ctp:29
msgid "Upgrading a 2.3 instance to 2.4"
msgstr ""
#: View/Pages/administration.ctp:30
msgid "Warning: Running this scripts below can result in the loss of data. Make sure that you back your database up before running them."
msgstr ""
#: View/Pages/administration.ctp:31
msgid "The order for the 2.4 upgrade procedure is"
msgstr ""
#: View/Pages/administration.ctp:33
msgid "%s - run this to migrate the 2.3 data to the 2.4 format"
msgstr ""
#: View/Pages/administration.ctp:33
msgid "Upgrade to 2.4"
msgstr ""
#: View/Pages/administration.ctp:34
msgid "If it completes successful, run the %s to remove the fields that are specific to 2.3. Make sure that the migration of the data to the 2.4 format was successful (you can check the result in the audit logs). If you have run the 2.4 upgrade script previously but are running into SQL errors on the column 'org', run this script."
msgstr ""
#: View/Pages/administration.ctp:34
msgid "2.3->2.4 clean-up script"
msgstr ""
#: View/Pages/administration.ctp:34
msgid "If the migration of your data from 2.4 is not complete this will lead to the loss of data. Backing your DB up is highly recommended. Are you ready to start removing the obsolete fields?"
msgstr ""
#: View/Pages/doc/administration.ctp:3
#: View/Pages/doc/categories_and_types.ctp:3
#: View/Pages/doc/concepts.ctp:3
#: View/Pages/doc/general.ctp:3
#: View/Pages/doc/quickstart.ctp:3;14
#: View/Pages/doc/user_management.ctp:3
#: View/Pages/doc/using_the_system.ctp:3
msgid "Quick Start"
msgstr ""
#: View/Pages/doc/administration.ctp:4
#: View/Pages/doc/categories_and_types.ctp:4
#: View/Pages/doc/concepts.ctp:4
#: View/Pages/doc/general.ctp:4;14
#: View/Pages/doc/quickstart.ctp:4
#: View/Pages/doc/user_management.ctp:4
#: View/Pages/doc/using_the_system.ctp:4
msgid "General Layout"
msgstr ""
#: View/Pages/doc/administration.ctp:5
#: View/Pages/doc/categories_and_types.ctp:5
#: View/Pages/doc/concepts.ctp:5;14
#: View/Pages/doc/general.ctp:5
#: View/Pages/doc/quickstart.ctp:5
#: View/Pages/doc/user_management.ctp:5
#: View/Pages/doc/using_the_system.ctp:5
msgid "General Concepts"
msgstr ""
#: View/Pages/doc/administration.ctp:6
#: View/Pages/doc/categories_and_types.ctp:6
#: View/Pages/doc/concepts.ctp:6
#: View/Pages/doc/general.ctp:6
#: View/Pages/doc/quickstart.ctp:6
#: View/Pages/doc/user_management.ctp:6
#: View/Pages/doc/using_the_system.ctp:6
msgid "User Management and Global actions"
msgstr ""
#: View/Pages/doc/administration.ctp:7
#: View/Pages/doc/categories_and_types.ctp:7
#: View/Pages/doc/concepts.ctp:7
#: View/Pages/doc/general.ctp:7
#: View/Pages/doc/quickstart.ctp:7
#: View/Pages/doc/user_management.ctp:13
#: View/Pages/doc/using_the_system.ctp:7;26
msgid "Using the system"
msgstr ""
#: View/Pages/doc/administration.ctp:10
msgid "Settings and Diagnostics"
msgstr ""
#: View/Pages/doc/administration.ctp:11;171
msgid "Blacklist"
msgstr ""
#: View/Pages/doc/administration.ctp:14
msgid "User Management"
msgstr ""
#: View/Pages/doc/administration.ctp:15
msgid "Role Management"
msgstr ""
#: View/Pages/doc/administration.ctp:16
msgid "Logging"
msgstr ""
#: View/Pages/doc/administration.ctp:17;202
#: View/Pages/doc/general.ctp:78
msgid "Administrative Tools"
msgstr ""
#: View/Pages/doc/administration.ctp:18;205
msgid "Background Processing"
msgstr ""
#: View/Pages/doc/administration.ctp:19
msgid "FAQ"
msgstr ""
#: View/Pages/doc/administration.ctp:22
#: View/Pages/doc/categories_and_types.ctp:9
#: View/Pages/doc/concepts.ctp:9
#: View/Pages/doc/general.ctp:9
#: View/Pages/doc/quickstart.ctp:9
#: View/Pages/doc/user_management.ctp:15
#: View/Pages/doc/using_the_system.ctp:22
msgid "Categories and Types"
msgstr ""
#: View/Pages/doc/administration.ctp:27
msgid "Server settings and diagnostics"
msgstr ""
#: View/Pages/doc/administration.ctp:28
msgid "Since version 2.3, MISP has a settings and diagnostics tool that allows site-admins to manage and diagnose their MISP installation. You can access this by navigating to Administration - Server settings"
msgstr ""
#: View/Pages/doc/administration.ctp:29
msgid "Server settings overview with all of the tabs explained."
msgstr ""
#: View/Pages/doc/administration.ctp:30
msgid "The settings and diagnostics tool is split up into several aspects, all accessible via the tabs on top of the tool. For any unset or incorrectly set setting, or failed diagnostic a number next to the tab name will indicate the number and severity of the issues. If the number is written with a red font, it means that the issue is critical. First, let's look at the various tabs"
msgstr ""
#: View/Pages/doc/administration.ctp:32
msgid "General overview of the current state of your MISP installation"
msgstr ""
#: View/Pages/doc/administration.ctp:33
msgid "MISP settings"
msgstr ""
#: View/Pages/doc/administration.ctp:33
msgid "Basic MISP settings. This includes the way MISP handles the default settings for distribution settings, whether background jobs are enabled, etc"
msgstr ""
#: View/Pages/doc/administration.ctp:34
msgid "GnuPG settings"
msgstr ""
#: View/Pages/doc/administration.ctp:34
msgid "GnuPG related settings."
msgstr ""
#: View/Pages/doc/administration.ctp:35
msgid "HTTP proxy related settings."
msgstr ""
#: View/Pages/doc/administration.ctp:36
msgid "Security settings"
msgstr ""
#: View/Pages/doc/administration.ctp:36
msgid "Settings controlling the brute-force protection and the application's salt key."
msgstr ""
#: View/Pages/doc/administration.ctp:37
msgid "Misc settings"
msgstr ""
#: View/Pages/doc/administration.ctp:37
msgid "You change the debug options here, but make sure that debug is always disabled on a production system."
msgstr ""
#: View/Pages/doc/administration.ctp:38
msgid "The diagnostics tool checks if all directories that MISP uses to store data are writeable by the apache user. Also, the tool checks whether the STIX libraries and GnuPG are working as intended."
msgstr ""
#: View/Pages/doc/administration.ctp:39
msgid "Shows the background workers (if enabled) and shows a warning if they are not running. Admins can also restart the workers here."
msgstr ""
#: View/Pages/doc/administration.ctp:40
msgid "Download a report in JSON format, compiled of all of the settings visible in the tool."
msgstr ""
#: View/Pages/doc/administration.ctp:42
msgid "The settings tabs explained."
msgstr ""
#: View/Pages/doc/administration.ctp:43
msgid "Each of the setting pages is a table with each row representing a setting. Coloured rows indicate that the setting is incorrect / not set and the colour determines the severity (red = critical, yellow = recommended, green = optional). The columns are as follows"
msgstr ""
#: View/Pages/doc/administration.ctp:45
msgid "The severity of the setting."
msgstr ""
#: View/Pages/doc/administration.ctp:46
msgid "The setting name."
msgstr ""
#: View/Pages/doc/administration.ctp:47
msgid "The current value of the setting."
msgstr ""
#: View/Pages/doc/administration.ctp:48
msgid "A description of what the setting does."
msgstr ""
#: View/Pages/doc/administration.ctp:49
msgid "If the setting is incorrect / not set, then this field will let the user know what is wrong."
msgstr ""
#: View/Pages/doc/administration.ctp:51
msgid "The workers tab."
msgstr ""
#: View/Pages/doc/administration.ctp:52
msgid "The workers tab shows a list of the workers that MISP can use. You can restart the workers using the restart all workers, If the button doesn't work, make sure that the workers were started using the apache user. This can however only be done using the command line, refer to the INSTALL.txt documentation on how to let the workers automatically start on each boot."
msgstr ""
#: View/Pages/doc/administration.ctp:54
msgid "Worker Type"
msgstr ""
#: View/Pages/doc/administration.ctp:54
msgid "The worker type is determined by the queue it monitors. MISP currently has 5 queues (cache, default, prio, email and a special _schdlr_ queue)."
msgstr ""
#: View/Pages/doc/administration.ctp:55
msgid "Worker Id"
msgstr ""
#: View/Pages/doc/administration.ctp:55
msgid "The ID is made up of the machine name, the PID of the worker and the queue it monitors."
msgstr ""
#: View/Pages/doc/administration.ctp:56
msgid "Displays OK if the worker is running. If the _schdlr_ worker is the only one not running make sure that you copy the config file into the cakeresque directory as described in the INSTALL.txt documentation."
msgstr ""
#: View/Pages/doc/administration.ctp:59
msgid "Import Blacklist"
msgstr ""
#: View/Pages/doc/administration.ctp:60
msgid "It is possible to ban certain values from ever being entered into the system via an event info field or an attribute value. This is done by blacklisting the value in this section."
msgstr ""
#: View/Pages/doc/administration.ctp:61;69
msgid "Adding and modifying entries"
msgstr ""
#: View/Pages/doc/administration.ctp:62
msgid "Administrators can add, edit or delete blacklisted items by using the appropriate functions in the list's action menu and the menu on the left."
msgid "They can be used for several things, such as unifying the capitalisation of file paths for more accurate event correlation or to automatically censor the usernames and use system path variable names (changing C:\\Users\\UserName\\Appdata\\Roaming\\file.exe to %APPDATA%\\file.exe).<br />\n"
"\t\tThe second use is blocking, if a regular expression is entered with a blank replacement, any event info or attribute value containing the expression will not be added. Please make sure the entered regexp expression follows the preg_replace pattern rules as described <a href=\"http://php.net/manual/en/function.preg-replace.php\">here</a>."
msgstr ""
#: View/Pages/doc/administration.ctp:70
msgid "Administrators can add, edit or delete regular expression rules, which are made up of a regex pattern that the system searches for and a replacement for the detected pattern."
msgstr ""
#: View/Pages/doc/administration.ctp:71
msgid "Add, edit or remove Regexp entries that will affect all newly created attributes here."
msgstr ""
#: View/Pages/doc/administration.ctp:73
msgid "Managing the Signature whitelist"
msgstr ""
#: View/Pages/doc/administration.ctp:74
msgid "The signature whitelist view, accessible through the administration menu on the left, allows administrators to create and maintain a list of addresses that are whitelisted from ever being added to the NIDS signatures. Addresses listed here will be commented out when exporting the NIDS list."
msgstr ""
#: View/Pages/doc/administration.ctp:75
msgid "Whitelisting an address"
msgstr ""
#: View/Pages/doc/administration.ctp:76
msgid "While in the whitelist view, click on New Whitelist on the left to bring up the add whitelist view to add a new address."
msgstr ""
#: View/Pages/doc/administration.ctp:77
msgid "Managing the list"
msgstr ""
#: View/Pages/doc/administration.ctp:78
msgid "When viewing the list of whitelisted addresses, the following pieces of information are shown: The ID of the whitelist entry (assigned automatically when a new address is added), the address itself that is being whitelisted and a set of controls allowing you to delete the entry or edit the address."
msgstr ""
#: View/Pages/doc/administration.ctp:79
msgid "You can edit or delete currently white-listed addresses using the action buttons on this list."
msgstr ""
#: View/Pages/doc/administration.ctp:81
msgid "Managing the users"
msgstr ""
#: View/Pages/doc/administration.ctp:82
msgid "As an admin, you can set up new accounts for users, edit the profiles of users, delete them, or just have a look at all the viewers' profiles. Organisation admins are restricted to executing the same actions on their organisation's users only."
msgstr ""
#: View/Pages/doc/administration.ctp:83
msgid "Adding a new user"
msgstr ""
#: View/Pages/doc/administration.ctp:84;114
msgid "To add a new user, click on the New User button in the administration menu to the left and fill out the following fields in the view that is loaded"
msgstr ""
#: View/Pages/doc/administration.ctp:85
msgid "Add user"
msgstr ""
#: View/Pages/doc/administration.ctp:85
msgid "Fill this form out to add a new user. Keep in mind that the drop-down menu titled Role controls the privileges the user will have."
msgstr ""
#: View/Pages/doc/administration.ctp:87;116
msgid "The user's e-mail address, this will be used as his/her login name and as an address to send all the automatic e-mails and e-mails sent by contacting the user as the reporter of an event."
msgstr ""
#: View/Pages/doc/administration.ctp:88
msgid "A temporary password for the user that he/she should change after the first login. Make sure that it is at least 6 characters long, includes a digit or a special character and contains at least one upper-case and at least one lower-case character."
msgstr ""
#: View/Pages/doc/administration.ctp:89;118
msgid "Confirm Password"
msgstr ""
#: View/Pages/doc/administration.ctp:89;118
msgid "This should be an exact copy of the Password field."
msgstr ""
#: View/Pages/doc/administration.ctp:90;119
msgid "The organisation of the user. Entering ADMIN into this field will give administrator privileges to the user. If you are an organisation admin, then this field will be unchangeable and be set to your own organisation."
msgstr ""
#: View/Pages/doc/administration.ctp:91;120;170
#: View/Roles/admin_index.ctp:2
#: View/Roles/index.ctp:2
msgid "Roles"
msgstr ""
#: View/Pages/doc/administration.ctp:91;120
msgid "A drop-down list allows you to choose a role-group that the user should belong to. Roles define the privileges of the user. To learn more about roles, <a href=#roles>click here</a>."
msgid "Receive alerts from \"contact reporter\" requests"
msgstr ""
#: View/Pages/doc/administration.ctp:93
msgid "This option will subscribe the new user to e-mails that are generated when another user tries to get in touch with an event's reporting organisation that matches that of the new user."
msgid "This is assigned automatically and is the unique authentication key of the user (he/she will be able to reset this and receive a new key). It is used for exports and for connecting one server to another, but it requires the user to be assigned to a role that has auth permission enabled."
msgstr ""
#: View/Pages/doc/administration.ctp:95;124
msgid "NIDS Sid"
msgstr ""
#: View/Pages/doc/administration.ctp:95;124
msgid "Nids ID, not yet implemented."
msgstr ""
#: View/Pages/doc/administration.ctp:96;127
msgid "GnuPGkey"
msgstr ""
#: View/Pages/doc/administration.ctp:96;127
msgid "The key used for encrypting e-mails sent through the system."
msgstr ""
#: View/Pages/doc/administration.ctp:98
msgid "Listing all users"
msgstr ""
#: View/Pages/doc/administration.ctp:99
msgid "To list all current users of the system, just click on List Users under the administration menu to the left. A view will be loaded with a list of all users and the following columns of information"
msgstr ""
#: View/Pages/doc/administration.ctp:100
msgid "List users"
msgstr ""
#: View/Pages/doc/administration.ctp:100
msgid "View, Edit or Delete a user using the action buttons to the right."
msgstr ""
#: View/Pages/doc/administration.ctp:102
msgid "The user's automatically assigned ID number."
msgstr ""
#: View/Pages/doc/administration.ctp:103
msgid "The organisation that the user belongs to."
msgstr ""
#: View/Pages/doc/administration.ctp:104
msgid "The e-mail address (and login name) of the user."
msgstr ""
#: View/Pages/doc/administration.ctp:105
#: View/Users/admin_view.ctp:29
#: View/Users/view.ctp:24
msgid "Autoalert"
msgstr ""
#: View/Pages/doc/administration.ctp:105
msgid "Shows whether the user has subscribed to auto-alerts and is always receiving the mass-emails regarding newly published events that he/she is eligible for."
msgstr ""
#: View/Pages/doc/administration.ctp:106
msgid "Shows whether the user has the subscription to contact reporter e-mails directed at his/her organisation turned on or off."
msgid "This flag indicates whether the user has accepted the terms of use or not."
msgstr ""
#: View/Pages/doc/administration.ctp:110
#: View/Users/admin_view.ctp:120
msgid "Newsread"
msgstr ""
#: View/Pages/doc/administration.ctp:110
msgid "The last point in time when the user has looked at the news section of the system."
msgstr ""
#: View/Pages/doc/administration.ctp:111
msgid "Action Buttons"
msgstr ""
#: View/Pages/doc/administration.ctp:111
msgid "Here you can view a detailed view of a user, edit the basic details of a user (same view as the one used for creating a new user, but all the fields come filled out by default) or remove a user completely."
msgstr ""
#: View/Pages/doc/administration.ctp:113
msgid "Editing a user"
msgstr ""
#: View/Pages/doc/administration.ctp:117
msgid "It is possible to assign a new password manually for a user. For example, in case that he/she forgot the old one a new temporary one can be assigned. Make sure to check the \"Change password\" field if you do give out a temporary password, so that the user will be forced to change it after login."
msgstr ""
#: View/Pages/doc/administration.ctp:121
msgid "This option will subscribe the user to automatically generated e-mails whenever an event is published."
msgstr ""
#: View/Pages/doc/administration.ctp:122
msgid "This option will subscribe the user to e-mails that are generated when another user tries to get in touch with an event's reporting organisation that matches that of the user."
msgstr ""
#: View/Pages/doc/administration.ctp:123
msgid "It is possible to request a new authentication key for the user."
msgstr ""
#: View/Pages/doc/administration.ctp:125
msgid "Indicates whether the user has accepted the terms of use already or not."
msgstr ""
#: View/Pages/doc/administration.ctp:126
msgid "Setting this flag will require the user to change password after the next login."
msgstr ""
#: View/Pages/doc/administration.ctp:129
msgid "Contacting a user"
msgstr ""
#: View/Pages/doc/administration.ctp:130
msgid "Site admins can use the \"Contact users\" feature to send all or an individual user an e-mail. Users that have a GnuPG key set will receive their e-mails encrypted. When clicking this button on the left, you'll be presented with a form that allows you to specify the type of the e-mail, who it should reach and what the content is using the following options"
msgid "This defines the type of the e-mail, which can be a custom message or a password reset. Password resets automatically include a new temporary password at the bottom of the message and will automatically change the user's password accordingly."
msgstr ""
#: View/Pages/doc/administration.ctp:134
msgid "Recipient"
msgstr ""
#: View/Pages/doc/administration.ctp:134
msgid "The recipient toggle lets you contact all your users, a single user (which creates a second drop-down list with all the e-mail addresses of the users) and potential future users (which opens up a text field for the e-mail address and a text area field for a GnuPG public key)."
msgstr ""
#: View/Pages/doc/administration.ctp:135;136
#: View/Users/admin_email.ctp:24
#: View/Users/admin_quick_email.ctp:15
msgid "Subject"
msgstr ""
#: View/Pages/doc/administration.ctp:135;136
msgid "In the case of a custom e-mail, you can enter a subject line here."
msgstr ""
#: View/Pages/doc/administration.ctp:137
msgid "Custom message checkbox"
msgstr ""
#: View/Pages/doc/administration.ctp:137
msgid "This is available for password resets, you can either write your own message (which will be appended with a temporary key and the signature), or let the system generate one automatically."
msgstr ""
#: View/Pages/doc/administration.ctp:139
msgid "Keep in mind that all e-mails sent through this system will, in addition to your own message, will be signed in the name of the instance's host organisation's support team, will include the e-mail address of the instance's support (if the contact field is set in the bootstrap file), and will include the instance's GnuPG signature for users that have a GnuPG key set (and thus are eligible for an encrypted e-mail)."
msgstr ""
#: View/Pages/doc/administration.ctp:141
msgid "Managing the roles"
msgstr ""
#: View/Pages/doc/administration.ctp:142
msgid "Privileges are assigned to users by assigning them to rule groups, which use one of four options determining what they can do with events and four additional privilege elevating settings. The four options for event manipulation are: Read Only, Manage My Own Events, Manage Organisation Events, Manage & Publish Organisation Events. The extra privileges are admin, sync, authentication key usage and audit permission"
msgstr ""
#: View/Pages/doc/administration.ctp:144
msgid "Read Only"
msgstr ""
#: View/Pages/doc/administration.ctp:144
msgid "This allows the user to browse events that his organisation has access to, but doesn't allow any changes to be made to the database."
msgstr ""
#: View/Pages/doc/administration.ctp:145
msgid "Manage My Own Events"
msgstr ""
#: View/Pages/doc/administration.ctp:145
msgid "The second option, gives its users rights to create, modify or delete their own events, but they cannot publish them."
msgstr ""
#: View/Pages/doc/administration.ctp:146
msgid "Manage Organization Events"
msgstr ""
#: View/Pages/doc/administration.ctp:146
msgid "Allows users to create events or modify and delete events created by a member of their organisation."
msgstr ""
#: View/Pages/doc/administration.ctp:147
msgid "Manage & Publish Organisation Events"
msgstr ""
#: View/Pages/doc/administration.ctp:147
msgid "This last setting, gives users the right to do all of the above and also to publish the events of their organisation."
msgstr ""
#: View/Pages/doc/administration.ctp:148
msgid "Perm sync"
msgstr ""
#: View/Pages/doc/administration.ctp:148
msgid "This setting allows the users of the role to be used as a synchronisation user. The authentication key of this user can be handed out to the administrator of a remote MISP instance to allow the synchronisation features to work."
msgstr ""
#: View/Pages/doc/administration.ctp:149
msgid "Perm auth"
msgstr ""
#: View/Pages/doc/administration.ctp:149
msgid "This setting enables the authentication key of the role's users to be used for rest requests."
msgstr ""
#: View/Pages/doc/administration.ctp:150
msgid "Perm admin"
msgstr ""
#: View/Pages/doc/administration.ctp:150
msgid "Gives the user limited administrator privileges, this setting is used for the organisation admins"
msgstr ""
#: View/Pages/doc/administration.ctp:151
msgid "Perm site admin"
msgstr ""
#: View/Pages/doc/administration.ctp:151
msgid "Gives the user full administrator privileges, this setting is used for the site admins."
msgstr ""
#: View/Pages/doc/administration.ctp:152
msgid "Perm audit"
msgstr ""
#: View/Pages/doc/administration.ctp:152
msgid "Grants access to the logs. With the exception of site admins, only logs generated by the user's own org are visible."
msgstr ""
#: View/Pages/doc/administration.ctp:153
msgid "Perm regexp access"
msgstr ""
#: View/Pages/doc/administration.ctp:153
msgid "Allows the users with this permission enabled to edit the regular expression table. Be careful when giving out this permission, incorrect regular expressions can be very harmful (infinite loops, loss of data, etc.)."
msgstr ""
#: View/Pages/doc/administration.ctp:154
msgid "Perm tagger"
msgstr ""
#: View/Pages/doc/administration.ctp:154
msgid "Allows the user with this permission to create custom tags and assign them to events."
msgstr ""
#: View/Pages/doc/administration.ctp:156
msgid "Creating roles"
msgstr ""
#: View/Pages/doc/administration.ctp:157
msgid "When creating a new role, you will have to enter a name for the role to be created and set up the permissions (as described above) using the radio toggle and the four check-boxes."
msgstr ""
#: View/Pages/doc/administration.ctp:158
msgid "Listing roles"
msgstr ""
#: View/Pages/doc/administration.ctp:159
msgid "By clicking on the List Roles button, you can view a list of all the currently registered roles and a list of the permission flags turned on for each. In addition, you can find buttons that allow you to edit and delete the roles. Keep in mind that you will need to first remove every member from a role before you can delete it."
msgstr ""
#: View/Pages/doc/administration.ctp:160
msgid "List roles"
msgstr ""
#: View/Pages/doc/administration.ctp:160
msgid "You can View, Edit or Delete roles using the action buttons to the right in each row. Keep in mind that a role has to be devoid of members before it can be deleted."
msgstr ""
#: View/Pages/doc/administration.ctp:162
msgid "Using the logs of MISP"
msgstr ""
#: View/Pages/doc/administration.ctp:163
msgid "Users with audit permissions are able to browse or search the logs that MISP automatically appends each time certain actions are taken (actions that modify data or if a user logs in and out)."
msgstr ""
#: View/Pages/doc/administration.ctp:164
msgid "Generally, the following actions are logged"
msgid "Listing all the log entries will show the following columns generated by the users of your organisation (or all organisations in the case of site admins)"
msgstr ""
#: View/Pages/doc/administration.ctp:178
msgid "List logs"
msgstr ""
#: View/Pages/doc/administration.ctp:178
msgid "Here you can view a list of all logged actions."
msgstr ""
#: View/Pages/doc/administration.ctp:180
msgid "The automatically assigned ID number of the entry."
msgstr ""
#: View/Pages/doc/administration.ctp:181
msgid "The e-mail address of the user whose actions triggered the entry."
msgstr ""
#: View/Pages/doc/administration.ctp:182
msgid "The organisation of the above mentioned user."
msgstr ""
#: View/Pages/doc/administration.ctp:183
msgid "The date and time when the entry originated."
msgstr ""
#: View/Pages/doc/administration.ctp:184
msgid "The action's type. This can include: login/logout for users, add, edit, delete for events, attributes, users and servers."
msgstr ""
#: View/Pages/doc/administration.ctp:185
msgid "The title of an event always includes the target type (Event, User, Attribute, Server), the target's ID and the target's name (for example: e-mail address for users, event description for events)."
msgstr ""
#: View/Pages/doc/administration.ctp:186
msgid "This field is only filled out for entries with the action being add or edit. The changes are detailed in the following format"
msgstr ""
#: View/Pages/doc/administration.ctp:188
msgid "When the entry is about the creation of a new item (such as adding a new event) then the change will look like this for example"
msgstr ""
#: View/Pages/doc/administration.ctp:191
msgid "Search log"
msgstr ""
#: View/Pages/doc/administration.ctp:191
msgid "You can search the logs using this form, narrow down your search by filling out several fields."
msgstr ""
#: View/Pages/doc/administration.ctp:192
msgid "Searching the Logs"
msgstr ""
#: View/Pages/doc/administration.ctp:193
msgid "Another way to browse the logs is to search it by filtering the results according to the following fields (the search is a sub-string search, the sub-string has to be an exact match for the entry in the field that is being searched for)"
msgstr ""
#: View/Pages/doc/administration.ctp:195
msgid "By searching by Email, it is possible to view the log entries of a single user."
msgstr ""
#: View/Pages/doc/administration.ctp:196
msgid "Searching for an organisation allows you to see all actions taken by any member of the organisation."
msgstr ""
#: View/Pages/doc/administration.ctp:197
msgid "With the help of this drop down menu, you can search for various types of actions taken (such as logins, deletions, etc)."
msgstr ""
#: View/Pages/doc/administration.ctp:198
msgid "There are several ways in which to use this field, since the title fields contain several bits of information and the search searches for any substrings contained within the field, it is possible to just search for the ID number of a logged event, the username / server's name / event's name / attribute's name of the event target."
msgstr ""
#: View/Pages/doc/administration.ctp:199
msgid "With the help of this field, you can search for various specific changes or changes to certain variables (such as published will find all the log entries where an event has gotten published, ip-src will find all attributes where a source IP address has been entered / edited, etc)."
msgstr ""
#: View/Pages/doc/administration.ctp:203
msgid "MISP has a couple of administrative tools that help administrators keep their instance up to date and healthy. The list of these small tools can change rapidly with each new version, but they should be self-explanatory. Make sure to check this section after upgrading to a new version, just in case there is a new upgrade script in there - though if this is the case it will be mentioned in the upgrade instructions."
msgstr ""
#: View/Pages/doc/administration.ctp:206
msgid "If enabled, MISP can delegate a lot of the time intensive tasks to the background workers. These will then be executed in order, allowing the users of the instance to keep using the system without a hiccup and without having to wait for the process to finish. It also allows for certain tasks to be scheduled and automated."
msgstr ""
#: View/Pages/doc/administration.ctp:207
msgid "Command Line Tools for the Background Workers"
msgstr ""
#: View/Pages/doc/administration.ctp:208
msgid "The background workers are powered by <a href=\"https://github.com/kamisama/Cake-Resque\">CakeResque</a>, so all of the CakeResque commands work.\n"
"\t\tTo start all of the workers needed by MISP go to your <code>/var/www/MISP/app/Console/worker</code> (assuming a standard installation path) and execute start.sh.\n"
"\t\tTo interact with the workers, here is a list of useful commands. Go to your <code>/var/www/MISP/app/Console</code> (assuming a standard installation path) and execute one of the following commands as a parameter to <code>./cake CakeResque.CakeResque</code> (for example: <code>./cake CakeResque.CakeResque tail</code>)"
msgstr ""
#: View/Pages/doc/administration.ctp:212
msgid "tail"
msgstr ""
#: View/Pages/doc/administration.ctp:212
msgid "tail the various log files that CakeResque creates, just choose the one from the list that you are interested in."
msgstr ""
#: View/Pages/doc/administration.ctp:213
msgid "cleanup"
msgstr ""
#: View/Pages/doc/administration.ctp:213
msgid "terminate the job that a worker is working on immediately. You will be presented with a choice of workers to choose from when executing this command."
msgstr ""
#: View/Pages/doc/administration.ctp:214
msgid "clear"
msgstr ""
#: View/Pages/doc/administration.ctp:214
msgid "Clear the queue of a worker immediately."
msgstr ""
#: View/Pages/doc/administration.ctp:215
msgid "stats"
msgstr ""
#: View/Pages/doc/administration.ctp:215
msgid "shows some statistics about your workers including the count of successful and failed jobs."
msgstr ""
#: View/Pages/doc/administration.ctp:217
msgid "The other commands should not be needed, instead of starting / stopping or restarting workers use the supplied start.sh (it stops all workers and starts them all up again). For further instructions on how to use the console commands for the workers, visit the <a href=\"http://cakeresque.kamisama.me/commands#cleanup\">CakeResque list of commands</a>."
msgstr ""
#: View/Pages/doc/administration.ctp:218
msgid "Monitoring the Background Processes"
msgstr ""
#: View/Pages/doc/administration.ctp:219
msgid "The \"Jobs\" menu item within the Administration menu allows site admins to get an overview of all of the currently and in the past scheduled jobs. Admins can see the status of each job, and what the queued job is trying to do. If a job fails, it will try to set an error message here too. The following columns are shown in the jobs table"
msgstr ""
#: View/Pages/doc/administration.ctp:221
msgid "The job's ID (this is the ID of the job's meta-data stored in the default data-store, not to be confused with the process ID stored in the redis database and used by the workers.)"
msgstr ""
#: View/Pages/doc/administration.ctp:222
msgid "Process"
msgstr ""
#: View/Pages/doc/administration.ctp:222
msgid "The process's ID."
msgstr ""
#: View/Pages/doc/administration.ctp:223
msgid "Worker"
msgstr ""
#: View/Pages/doc/administration.ctp:223
msgid "The name of the worker queue. There are 3+1 workers running if background jobs are enabled: default, cache, email, and a special Scheduler (this should never show up in the jobs table)."
msgstr ""
#: View/Pages/doc/administration.ctp:224
msgid "Job Type"
msgstr ""
#: View/Pages/doc/administration.ctp:224
msgid "The name of the queued job."
msgstr ""
#: View/Pages/doc/administration.ctp:225
msgid "Shows a basic input handled by the job - such as \"Event:50\" for a publish email alert job for event 50."
msgstr ""
#: View/Pages/doc/administration.ctp:226
msgid "This will show what the job is currently doing or alternatively an error message describing why a job failed."
msgstr ""
#: View/Pages/doc/administration.ctp:227
msgid "The string identifier of the organisation that has scheduled the job."
msgstr ""
#: View/Pages/doc/administration.ctp:228
msgid "The status reported by the worker."
msgstr ""
#: View/Pages/doc/administration.ctp:229
msgid "Retries"
msgstr ""
#: View/Pages/doc/administration.ctp:229
msgid "Currently unused, it is planned to introduced automatic delayed retries for the background processing to add resilience."
msgstr ""
#: View/Pages/doc/administration.ctp:230
msgid "A progress bar showing how the job is coming along."
msgstr ""
#: View/Pages/doc/administration.ctp:233
msgid "Scheduling Jobs and Recurring Jobs"
msgstr ""
#: View/Pages/doc/administration.ctp:234
msgid "Apart from off-loading long-lasting jobs to the background workers, there is a second major benefit of enabling the background workers: Site-administrators can schedule recurring tasks for the jobs that generally take the longest to execute. At the moment this includes pushing / pulling other instances and generating a full export cache for every organisation and export type. MISP comes with these 3 tasks pre-defined, but further tasks are planned. The following fields make up the scheduled tasks table"
msgstr ""
#: View/Pages/doc/administration.ctp:236
msgid "The ID of the task."
msgstr ""
#: View/Pages/doc/administration.ctp:237
msgid "The type of the task."
msgstr ""
#: View/Pages/doc/administration.ctp:238
msgid "Frequency"
msgstr ""
#: View/Pages/doc/administration.ctp:238
msgid "This number sets how often the job should be executed in hours. Setting this to 168 and picking the next execution on Sunday at 01:00 would execute the task every Sunday at 1 AM. Setting this value to 0 will make the task only run once on the scheduled date / time without rescheduling it afterwards."
msgstr ""
#: View/Pages/doc/administration.ctp:239
msgid "Scheduled Time"
msgstr ""
#: View/Pages/doc/administration.ctp:239
msgid "The time (in 24h format) when the task should be executed the next time it runs (and all consecutive times if a multiple of 24 is chosen for frequency)."
msgid "The date on which the task should be executed."
msgstr ""
#: View/Pages/doc/administration.ctp:241
msgid "A brief description of the task."
msgstr ""
#: View/Pages/doc/administration.ctp:242
msgid "This field shows when the job was queued by the scheduler for execution."
msgstr ""
#: View/Pages/doc/administration.ctp:244
msgid "Site administrators can schedule reccuring tasks on this page."
msgstr ""
#: View/Pages/doc/administration.ctp:245
msgid "Frequently asked questions"
msgstr ""
#: View/Pages/doc/administration.ctp:246
msgid "Losing access to the platform and resetting the password"
msgstr ""
#: View/Pages/doc/administration.ctp:247
msgid "If you ever lock yourself out of MISP as a site admin, there is a command line tool to reset your password. This can also be handy if you have changed the salt key and invalidated all of the passwords."
msgstr ""
#: View/Pages/doc/administration.ctp:248
msgid "Simply run the command"
msgstr ""
#: View/Pages/doc/administration.ctp:249
msgid "my_new_password"
msgstr ""
#: View/Pages/doc/administration.ctp:250
msgid "This will create a new password hash using the currently set salt."
msgstr ""
#: View/Pages/doc/categories_and_types.ctp:13
msgid "Attribute Categories and Types"
msgstr ""
#: View/Pages/doc/categories_and_types.ctp:14
#: View/Pages/doc/md/categories_and_types.ctp:1
msgid "Attribute Categories vs. Types"
msgstr ""
#: View/Pages/doc/categories_and_types.ctp:80
msgid "Click here to get the .md version for gitbook generation."
msgstr ""
#: View/Pages/doc/concepts.ctp:15
msgid "Admins and Site Admins"
msgstr ""
#: View/Pages/doc/concepts.ctp:16
msgid "There are two types of admins in MISP: Admins (also refered to as org admins) and Site Admins. Whilst the former can only do some limited administration of users of his/her own organisation, site admins have access to all of the features and data of the system. They are in charge of making sure that the system runs correctly and the maintenance of MISP."
msgstr ""
#: View/Pages/doc/concepts.ctp:17
msgid "Background Jobs"
msgstr ""
#: View/Pages/doc/concepts.ctp:18
msgid "A lot of the heavier tasks are a burden to users, in that their actions can cause long delays (and in some cases timeouts) while the application logic is executing. To alleviate this, long processes have been (if enabled) moved to background jobs, meaning that their execution happens asynchronously in the background, allowing the user to freely interact with the platform whilst the request is being processed."
msgstr ""
#: View/Pages/doc/concepts.ctp:19
msgid "MISP Instance"
msgstr ""
#: View/Pages/doc/concepts.ctp:20
msgid "A MISP instance is an installation of the MISP software and the connected database. All the data visible to the users is stored locally in the database and data that is shareable (based on the distribution settings) can be synchronised with other instances via the Sync actions. The instance that you are reading this manual on will be refered to as \"this instance\" or \"your instance\". The instances that your instance synchronises with will be refered to as \"remote instances\"."
msgstr ""
#: View/Pages/doc/concepts.ctp:21
msgid "Organisation administrators and Site administrators"
msgstr ""
#: View/Pages/doc/concepts.ctp:22
msgid "We have two types of administrators, site and organisation admins. The former has access to every administrator feature for all the data located on the system including global features such as the creation and modification of user roles and instance links, whilst organisation admins can administer users, events and logs of their own respective organisations."
msgstr ""
#: View/Pages/doc/concepts.ctp:23
msgid "Pivot path"
msgstr ""
#: View/Pages/doc/concepts.ctp:24
msgid "The (branching) path taken by a user from event to event while following correlation links. This is represented by the branching graph in the event view."
msgstr ""
#: View/Pages/doc/concepts.ctp:25
msgid "Pivoting"
msgstr ""
#: View/Pages/doc/concepts.ctp:26
msgid "The act of navigating from event to event through correlation links.\n"
msgstr ""
#: View/Pages/doc/concepts.ctp:29
msgid "Each event can only be directly edited by users of the original creator organisation (and site admins). However, if another organisation would like to amend an event with extra information on an event, or if they'd like to correct a mistake in an attribute, they can create a Proposal. These proposals could then be accepted by the original creator organisation. These proposals can be pulled to another server, allowing users on connected instances to propose changes which then could be accepted by the original creators on another instance (and subsequently pushed back)."
msgstr ""
#: View/Pages/doc/concepts.ctp:30
msgid "Publishing"
msgstr ""
#: View/Pages/doc/concepts.ctp:31
msgid "When an event is first created by a user, it is visible to everyone on the instance based on the access rights (\"Your organisation only\" events will not be visible to users of other organisations), but they will not be synchronised and they won't be exportable. For this, a user with publishing permission of the organisation that created the event has to publish the event. The system will then inform all the users of the instance that are subscribing to e-mail notifications and who have access to view the published event via an e-mail."
msgid "Pulling is the process of using the configured sync user on a remote instance to REST GET all of the accessible data (based on the distribution rights) to your instance and store it."
msgid "Pushing is the process of using a configured instance link to send an event or all accessible events (limited by the distribution rights) through the REST interface to a remote instance."
msgstr ""
#: View/Pages/doc/concepts.ctp:37
msgid "Certain common tasks can be scheduled for a later execution or for regular recurring executions. These tasks currently include caching all of the export formats, pulling from all eligible instances and pushing to all eligible instances."
msgstr ""
#: View/Pages/doc/concepts.ctp:38
msgid "Sync User"
msgstr ""
#: View/Pages/doc/concepts.ctp:39
msgid "A user of a role that grants sync permissions, these users (and their authentication keys) are used to serve as the points of connection between instances. Events pushed to an instance are pushed to a sync user, who then creates the events on the remote instance. Events pulled are added by the sync user that is used to connect the remote instance to your instance. As an administrator, keep in mind that a sync user needs auth key and publish permissions, has to have undergone the mandatory password change and has to have accepted the Terms of Use in order for the sync to work. Please make sure that all of these steps are taken before attempting to push or pull."
msgstr ""
#: View/Pages/doc/concepts.ctp:40
msgid "Synchronisation"
msgstr ""
#: View/Pages/doc/concepts.ctp:41
msgid "What we call synchronisation is an exchange of data between two (or more) MISP instances through our pull and push mechanisms."
msgid "Users with tagging rights can assigned various dynamically created tags to events, allowing an arbitrary link between events to be created. It is possible to filter events based on these tags and they can also be used to filter events for the automation."
msgid "Users with templating rights can create easy to fill forms that help with the event creation process."
msgstr ""
#: View/Pages/doc/general.ctp:15
msgid "The top bar"
msgstr ""
#: View/Pages/doc/general.ctp:16
msgid "This is the main menu that will be accessible from all of the views. In some instances, some additional buttons that will appear on top of these when a view provides it."
msgstr ""
#: View/Pages/doc/general.ctp:17
msgid "This menu contains all of the main functions of the site as a series of dropdown menus. These contains all (from the current user's perspective) accessible functions sorted into several groups."
msgstr ""
#: View/Pages/doc/general.ctp:19
msgid "Home button"
msgstr ""
#: View/Pages/doc/general.ctp:19
msgid "This button will return you to the start screen of the application, which is the event index page (more about this later)."
msgstr ""
#: View/Pages/doc/general.ctp:20
msgid "Event Actions"
msgstr ""
#: View/Pages/doc/general.ctp:20
msgid "All the malware data entered into MISP is made up of an event object that is described by its connected attributes. The Event actions menu gives access to all the functionality that has to do with the creation, modification, deletion, publishing, searching and listing of events and attributes."
msgstr ""
#: View/Pages/doc/general.ctp:21
msgid "Input filters alter what and how data can be entered into this instance. Apart from the basic validation of attribute entry by type, it is possible for the site administrators to define regular expression replacements and blacklists for certain values in addition to blocking certain values from being exportable. Users can view these replacement and blacklist rules here whilst administrator can alter them."
msgstr ""
#: View/Pages/doc/general.ctp:22;54
msgid "Global Actions"
msgstr ""
#: View/Pages/doc/general.ctp:22
msgid "This menu gives you access to information about MISP and this instance. You can view and edit your own profile, view the manual, read the news or the terms of use again, see a list of the active organisations on this instance and a histogram of their contributions by attribute type."
msgstr ""
#: View/Pages/doc/general.ctp:23;66
msgid "Sync Actions"
msgstr ""
#: View/Pages/doc/general.ctp:23
msgid "With administrator access rights, shows a list of the connected instances and allows the initiation of a push and a pull (more about the synchronisation mechanisms later)."
msgstr ""
#: View/Pages/doc/general.ctp:24
msgid "Administrators can add, edit or remove user accounts and user roles. Roles define the access rights to certain features such as publishing of events, usage of the REST interface or synchronisation of any user belonging to the given role. Site administrators can also access a contact form, through which it is possible to reset the passwords of users, or to just get in touch with them via encrypted e-mails."
msgstr ""
#: View/Pages/doc/general.ctp:25
msgid "If you have audit permissions, you can view the logs for your organisation (or for site admins for the entire system) here or even search the logs if you are interested in something specific."
msgstr ""
#: View/Pages/doc/general.ctp:26;90
#: View/Threads/index.ctp:2
msgid "Discussions"
msgstr ""
#: View/Pages/doc/general.ctp:26
msgid "Link to the discussion threads."
msgstr ""
#: View/Pages/doc/general.ctp:27
msgid "Proposal Notifications"
msgstr ""
#: View/Pages/doc/general.ctp:27
msgid "This shows how many proposals your organisation has received and across how many events they are spread out. Clicking this will take you to the list of proposals."
msgstr ""
#: View/Pages/doc/general.ctp:28
msgid "Logs you out of the system."
msgstr ""
#: View/Pages/doc/general.ctp:31
msgid "A list of the contents of each of the above drop-down menus"
msgstr ""
#: View/Pages/doc/general.ctp:32
msgid "Event actions"
msgstr ""
#: View/Pages/doc/general.ctp:34
msgid "Lists all the events in the system that are not private or belong to your organisation. You can add, modify, delete, publish or view individual events from this view."
msgstr ""
#: View/Pages/doc/general.ctp:35
msgid "Allows you to fill out an event creation form and create the event object, which you can start populating with attributes."
msgstr ""
#: View/Pages/doc/general.ctp:36
msgid "Lists all the attributes in the system that are not private or belong to your organisation. You can modify, delete or view each individual attribute from this view."
msgstr ""
#: View/Pages/doc/general.ctp:37
msgid "You can set search terms for a filtered attribute index view here."
msgstr ""
#: View/Pages/doc/general.ctp:38
msgid "Shows a list of all proposals that you are eligible to see."
msgstr ""
#: View/Pages/doc/general.ctp:39
msgid "Shows all of the events created by your organsiation that has pending proposals."
msgstr ""
#: View/Pages/doc/general.ctp:40
msgid "List all the tags that have been created by users with tag creation rights on this instance."
msgstr ""
#: View/Pages/doc/general.ctp:41
msgid "Create a new tag."
msgstr ""
#: View/Pages/doc/general.ctp:42
msgid "List all of the templates created by users with template creation rights on this instance."
msgstr ""
#: View/Pages/doc/general.ctp:43
msgid "Create a new template."
msgstr ""
#: View/Pages/doc/general.ctp:44
msgid "Export the data accessible to you in various formats."
msgstr ""
#: View/Pages/doc/general.ctp:45
msgid "If you have authentication key access, you can view how to use your key to use the REST interface for automation here."
msgstr ""
#: View/Pages/doc/general.ctp:48
msgid "Input filters"
msgstr ""
#: View/Pages/doc/general.ctp:50
msgid "You can view the Regular Expression rules, which modify the data that can be entered into the system. This can and should be used to help filter out personal information from automatic imports (such as removing the username from windows file paths), having unified representation for certain common values for easier correlation or simply standardising certain input. It is also possible to block certain values from being inserted. As a site administrator or a user with regex permission, you can also edit these rules."
msgstr ""
#: View/Pages/doc/general.ctp:51
msgid "You can view the whitelist rules, which contain the values that are blocked from being used for exports and automation on this instance. Site administrators have access to editing this list."
msgstr ""
#: View/Pages/doc/general.ctp:56
msgid "Read about the latest news regarding the MISP system."
msgstr ""
#: View/Pages/doc/general.ctp:57
msgid "Manage your user account."
msgstr ""
#: View/Pages/doc/general.ctp:58
msgid "Attribute Histogram"
msgstr ""
#: View/Pages/doc/general.ctp:58
msgid "View some statistics about the currently stored attributes."
msgstr ""
#: View/Pages/doc/general.ctp:59
msgid "You can view the role permissions here."
msgstr ""
#: View/Pages/doc/general.ctp:60
msgid "A link to this user guide."
msgstr ""
#: View/Pages/doc/general.ctp:61
msgid "View the terms & conditions again."
msgstr ""
#: View/Pages/doc/general.ctp:62
msgid "View a series of statistics about the users and the data on this instance."
msgstr ""
#: View/Pages/doc/general.ctp:63
msgid "Logs the current user out."
msgstr ""
#: View/Pages/doc/general.ctp:68
msgid "Connect your MISP instance to other instances, or view and modify the currently established connections."
msgstr ""
#: View/Pages/doc/general.ctp:73
msgid "New User"
msgstr ""
#: View/Pages/doc/general.ctp:73
msgid "Create an account for a new user for your organisation. Site administrators can create users for any organisation."
msgstr ""
#: View/Pages/doc/general.ctp:74
msgid "View, modify or delete the currently registered users."
msgstr ""
#: View/Pages/doc/general.ctp:75
msgid "New Role"
msgstr ""
#: View/Pages/doc/general.ctp:75
msgid "Create a new role group for the users of this instance, controlling their privileges to create, modify, delete and to publish events and to access certain features such as the logs or automation."
msgstr ""
#: View/Pages/doc/general.ctp:76
msgid "List, modify or delete currently existing roles."
msgstr ""
#: View/Pages/doc/general.ctp:77
msgid "You can use this view to send messages to your current or future users or send them a new temporary password."
msgstr ""
#: View/Pages/doc/general.ctp:78
msgid "Various tools, upgrade scripts that can help a site-admin run the instance."
msgstr ""
#: View/Pages/doc/general.ctp:79
msgid "Server Settings"
msgstr ""
#: View/Pages/doc/general.ctp:79
msgid "Set up and diagnose your MISP installation."
msgstr ""
#: View/Pages/doc/general.ctp:80
msgid "View the background jobs and their progress."
msgstr ""
#: View/Pages/doc/general.ctp:81
msgid "Schedule the pre-defined tasks for your instance (this currently includes export caching, server pull and server push)."
msgstr ""
#: View/Pages/doc/general.ctp:86
msgid "View the logs of the instance."
msgstr ""
#: View/Pages/doc/general.ctp:87
msgid "Search the logs by various attributes."
msgstr ""
#: View/Pages/doc/general.ctp:92
msgid "List all of the discussion threads."
msgstr ""
#: View/Pages/doc/general.ctp:93
msgid "Create a new discussion thread."
msgstr ""
#: View/Pages/doc/general.ctp:95
msgid "The left bar"
msgstr ""
#: View/Pages/doc/general.ctp:96
msgid "This bar changes based on each page-group. The blue selection shows you what page you are on."
msgstr ""
#: View/Pages/doc/quickstart.ctp:15
msgid "The Malware Information Sharing Platform (MISP) is the tool which will be used to facilitate the exchange of Indicator of Compromise (IOC) about\n"
"targeted malware and attacks within your community of trusted members. It is a central Indicator of Compromise (IOC) database with technical and\n"
"non-technical information. Exchanging this information should result in faster detection of targeted attacks and improve the detection ratio,\n"
"while also reducing the number of false positives."
msgstr ""
#: View/Pages/doc/quickstart.ctp:19
msgid "Create an Event"
msgstr ""
#: View/Pages/doc/quickstart.ctp:21
msgid "Browsing past Events"
msgstr ""
#: View/Pages/doc/quickstart.ctp:23
msgid "Export Events for logsearches"
msgstr ""
#: View/Pages/doc/user_management.ctp:8;21
msgid "First run of the system"
msgstr ""
#: View/Pages/doc/user_management.ctp:9;34
msgid "Managing your account"
msgstr ""
#: View/Pages/doc/user_management.ctp:10;48
msgid "Staying up to date"
msgstr ""
#: View/Pages/doc/user_management.ctp:19
msgid "User Management and Global Actions"
msgstr ""
#: View/Pages/doc/user_management.ctp:22
msgid "When first logging into MISP with the username and password provided by your administrator, there are a number of things that need to be done, before you can start using the system."
msgstr ""
#: View/Pages/doc/user_management.ctp:24
msgid "Accepting the Terms of use"
msgstr ""
#: View/Pages/doc/user_management.ctp:24
msgid "The terms of use are shown immediately after logging in for the first time, make sure to read through this page before clicking \"Accept Terms\" at the bottom of the page."
msgstr ""
#: View/Pages/doc/user_management.ctp:25;26;41
msgid "Changing the password"
msgstr ""
#: View/Pages/doc/user_management.ctp:25
msgid "After accepting the ToU, you'll be prompted to change your password, but keep in mind that it has to be at least 6 characters long, it has to include at least one upper-case and one lower-case character in addition to a digit or a special character. Enter the same password into the confirm password field, before clicking submit to finalise the change."
msgid "In order for the system to be able to encrypt the messages that you send through it, it needs to know your GnuPG key. Navigate to the Edit profile view (My Profile on the left -> Edit profile in the top right corner). Paste the key into the GnuPG field and click submit."
msgid "Turning auto-alerts on will allow the system to send you e-mail notifications about any new public events entered into the system by other users and private events added by members of your organisation. To turn this on, navigate to the Edit profile view (My profile on the left navigation menu -> Edit profile in the top right corner). Tick the auto-alert checkbox and click submit to enable this feature."
msgstr ""
#: View/Pages/doc/user_management.ctp:29
msgid "Use these checkboxes to subscribe to auto-alerts and contact reporter e-mails."
msgstr ""
#: View/Pages/doc/user_management.ctp:30;43
msgid "Subscribing to e-mails sent via the \"Contact Reporter\" functionality"
msgstr ""
#: View/Pages/doc/user_management.ctp:30
msgid "This feature is turned on right below the autoalerts and will allow you to receive e-mails addressed to your organisation whenever a user tries to ask about an event that was posted by a user of your organisation. Keep in mind that you can still be addressed by such a request even when this setting is turned off, if someone tries to contact you as the event creator directly or your organisation for an event that you personally have created then you will be notified."
msgstr ""
#: View/Pages/doc/user_management.ctp:31
msgid "Reviewing the Terms & Conditions"
msgstr ""
#: View/Pages/doc/user_management.ctp:31
msgid "o review the Terms & Conditions or to read the User Guide, use the appropriate button on the left navigation menu."
msgstr ""
#: View/Pages/doc/user_management.ctp:32
msgid "Making sure that compatibility mode is turned off (IE9&IE10)"
msgstr ""
#: View/Pages/doc/user_management.ctp:32
msgid "Compatibility mode can cause some elements to appear differently than intended or not appear at all. Make sure you have this option turned off."
msgstr ""
#: View/Pages/doc/user_management.ctp:35
msgid "To alter any details regarding your profile, use the \"My Profile\" menu button to bring up the profile overview and then click on \"Edit Profile\" in the right upper corner."
msgstr ""
#: View/Pages/doc/user_management.ctp:38
msgid "Change any of your profile settings here."
msgstr ""
#: View/Pages/doc/user_management.ctp:40
msgid "Changing your e-mail address"
msgstr ""
#: View/Pages/doc/user_management.ctp:40
msgid "Your e-mail address serves as both a login name and as a means of communication with other users of the MISP system via the contact reporter feature. To change your e-mail address, just enter the edit profile menu (My profile on the left navigation menu -> Edit profile in the top right corner) and change the field titled Email."
msgstr ""
#: View/Pages/doc/user_management.ctp:41
msgid "As a next step, change the password provided by your administrator to something of your own choosing. Click on My profile on the left navigation menu, under Global Actions, which will bring up the User view. Click on Edit User on the left navigation menu or Edit Profile in the top right corner. This next screen, allows you to edit your details, including your password, by filling out the password field. Keep in mind that the password has to be at least 6 characters long, has to include at least one upper-case and one lower-case character in addition to a digit or a special character. Enter the same password into the confirm password field, before clicking submit to finalise the change."
msgstr ""
#: View/Pages/doc/user_management.ctp:43
msgid "Turning this feature on will allow you to receive e-mails addressed to your organisation whenever a user tries to ask about an event that was posted by a user of your organisation. Keep in mind that you can still be addressed by such a request even when this setting is turned off, if someone tries to contact the person that reported an event that you yourself have created."
msgid "In order for the system to be able to encrypt the messages that you send through it, it needs to know your GnuPG key. You can acquire this by clicking on the GnuPG key link at the bottom left of the screen. Copy the entirety of the key and navigate to the Edit profile view (My Profile on the left -> Edit profile in the top right corner). Paste the key into the GnuPG field and click submit."
msgid "It is possible to make the system generate a new authentication key for you (for example if your previous one gets compromised. This can be accessed by clicking on the My Profile button and then clicking the reset key next to the currently active authentication code. The old key will become invalid when the new one is generated."
msgstr ""
#: View/Pages/doc/user_management.ctp:46
msgid "Clicking on reset will generate a new key for you and invalidate the old one, blocking it from being used."
msgstr ""
#: View/Pages/doc/user_management.ctp:49
msgid "MISP also provides its users with some information about itself and its users through the links provided in the Global Actions menu."
msgstr ""
#: View/Pages/doc/user_management.ctp:51
msgid "To read about the news regarding the system itself, click on News on the left menu. This will bring up a list of news items concerning updates and changes to MISP itself."
msgstr ""
#: View/Pages/doc/user_management.ctp:52
msgid "Member statistics"
msgstr ""
#: View/Pages/doc/user_management.ctp:52
msgid "By using the Attribute Histogram menu button on the left, you can see a quick histogram depicting the distribution of attribute types created by each organisation."
msgstr ""
#: View/Pages/doc/user_management.ctp:53
msgid "The user guide is also accessible via the Global Actions menu. You can find out more about how to use the system by reading this."
msgstr ""
#: View/Pages/doc/user_management.ctp:54
msgid "It is possible to review the terms & conditions that were shown during the first run of the system by clicking on the terms & conditions link in the Global Actions menu."
msgstr ""
#: View/Pages/doc/user_management.ctp:55
msgid "View statistics about the users and the data contained within this instance."
msgstr ""
#: View/Pages/doc/user_management.ctp:58
msgid "General Statistics"
msgstr ""
#: View/Pages/doc/user_management.ctp:58
msgid "View a set of statistics such as the number of Events and Attributes currently in existance on the platform. The number in the bracket shows the number of new items added during this week."
msgstr ""
#: View/Pages/doc/user_management.ctp:61
#: View/Users/statistics.ctp:42
#: View/Users/statistics_data.ctp:47
msgid "Activity Heatmap"
msgstr ""
#: View/Pages/doc/user_management.ctp:61
msgid "This graph shows a heatmap of all activity related to creating event related data on a day by day basis. By default, the graph shows the sum of the contributions of all organisations, but using the buttons representing each organisation in existance on the platform you can switch to the activity heatmap of a single organisation. If you'd like to see the activity further back in the past, just use the arrow buttons to navigate the heatmap."
msgstr ""
#: View/Pages/doc/user_management.ctp:66
msgid "Inspecting the input filters"
msgstr ""
#: View/Pages/doc/user_management.ctp:67
msgid "All the events and attributes that get entered into MISP will be run through a series of input filters. These are defined by the site administrators or users with special privileges to edit the filters, but every user can take a look at the currently active lists."
msgstr ""
#: View/Pages/doc/user_management.ctp:69
msgid "All Attribute value and Event info fields will be parsed for a set of regular expressions and replaced based on the replacement values contained in this section. This has many uses, such as unifying similar data for better correlation, removing personal data from file-paths or simply for clarity. It is also possible to blacklist data by not defining a replacement for a regular expression."
msgstr ""
#: View/Pages/doc/user_management.ctp:70
msgid "This list (can) contain a set of addresses that are allowed to be entered as attribute values but will be blocked from being exported to NIDS-es."
msgid "The process of entering an event can be split into 3 phases, the creation of the event itself, populating it with attributes\n"
"and attachments and finally publishing it."
msgstr ""
#: View/Pages/doc/using_the_system.ctp:30
msgid "During this first step, you will be create a basic event without any actual attributes, but storing general information such as a description, time and risk level of the incident. To start creating the event, click on the New Event button on the left and fill out the form you are presented with. The following fields need to be filled out"
msgstr ""
#: View/Pages/doc/using_the_system.ctp:31
msgid "Fill this form out to create a skeleton event, before proceeding to populate it with attributes and attachments."
msgstr ""
#: View/Pages/doc/using_the_system.ctp:33
msgid "The date when the incident has happened. Just click this field and a date-picker will pop up where you can select the desired date."
msgstr ""
#: View/Pages/doc/using_the_system.ctp:35
msgid "This setting controls, who will be able to see this event once it becomes published and eventually when it becomes pulled.\n"
"\t\t\t\t\t\tApart from being able to set which users on this server are allowed to see the event, this also controls whether\n"
"\t\t\t\t\t\tthe event will be synchronised to other servers or not. The distribution is inherited by attributes: the most restrictive setting wins.\n"
"\t\t\t\t\t\tThe following options are available"
msgstr ""
#: View/Pages/doc/using_the_system.ctp:41
msgid "Your organization only"
msgstr ""
#: View/Pages/doc/using_the_system.ctp:41
msgid "This setting will only allow members of your organisation to see this. It can be pulled to another instance by one of your organisation members where only your organisation will be able to see it.\n"
"\t\t\t\t\t\t\tEvents with this setting will not be synchronised"
msgstr ""
#: View/Pages/doc/using_the_system.ctp:43
msgid "Upon push: do not push. Upon pull : pull."
msgstr ""
#: View/Pages/doc/using_the_system.ctp:45
msgid "This Community-only"
msgstr ""
#: View/Pages/doc/using_the_system.ctp:45
msgid "Users that are part of your MISP community will be able to see the event.\n"
"\t\t\t\t\t\t\tThis includes your own organisation, organisations on this MISP server and organisations running MISP\n"
"\t\t\t\t\t\t\tservers that synchronise with this server. Any other organisations connected to such linked servers will\n"
"\t\t\t\t\t\t\tbe restricted from seeing the event"
msgstr ""
#: View/Pages/doc/using_the_system.ctp:49
msgid "Upon push: do not push. Upon pull: pull and downgrade to Your organization only."
msgstr ""
#: View/Pages/doc/using_the_system.ctp:51
msgid "Users that are part of your MISP community will be able to see the event.\n"
"\t\t\t\t\t\t\tThis includes all organisations on this MISP server, all organisations on MISP servers synchronising\n"
"\t\t\t\t\t\t\twith this server and the hosting organisations of servers that connect to those afore mentioned servers\n"
"\t\t\t\t\t\t\t(so basically any server that is 2 hops away from this one). Any other organisations connected to linked\n"
"\t\t\t\t\t\t\tservers that are 2 hops away from this own will be restricted from seeing the event."
msgstr ""
#: View/Pages/doc/using_the_system.ctp:56
msgid "Upon push: downgrade to This Community only and push. Upon pull: pull and downgrade to This Community only."
msgstr ""
#: View/Pages/doc/using_the_system.ctp:58
msgid "This will share the event with all MISP communities, allowing the event to be\n"
"\t\t\t\t\t\t\tfreely propagated from one server to the next."
msgstr ""
#: View/Pages/doc/using_the_system.ctp:60
msgid "Upon push: push. Upon pull: pull."
msgstr ""
#: View/Pages/doc/using_the_system.ctp:64
msgid "This field indicates the risk level of the event. Incidents can be categorised into three different threat categories (low, medium, high). This field can alternatively be left as undefined. The 3 options are"
msgid "The info field, where the malware/incident can get a brief description starting with the internal reference. This field should be as brief and concise as possible, the more detailed description happens through attributes in the next stage of the event's creation. Keep in mind that the system will automatically replace detected text strings that match a regular expression entry set up by your server's administrator(s)."
msgid "The second step of creating an event is to populate it with attributes and attachments. This can be done by adding them manually or importing the attributes from an external format (OpenIOC, ThreatConnect). To import from an external format or to upload an attachment use the options in the menu on the left."
msgid "Using the above shown buttons, you can populate an event using various tools that will be explained in the following section. Let's start with the Add Attribute button."
msgid "Keep in mind that the system searches for regular expressions in the value field of all attributes when entered, replacing detected strings within it as set up by the server's administrator (for example to enforce standardised capitalisation in paths for event correlation or to bring exact paths to a standardised format). The following fields need to be filled out"
msgid "This drop-down menu explains the category of the attribute, meaning what aspect of the malware this attribute is describing. This could mean the persistence mechanisms of the malware or network activity, etc. For a list of valid categories, %s"
msgid "Whilst categories determine what aspect of an event they are describing, the Type explains by what means that aspect is being described. As an example, the source IP address of an attack, a source e-mail address or a file sent through an attachment can all describe the payload delivery of a malware. These would be the types of attributes with the category of payload deliver. For an explanation of what each of the types looks like together with the valid combinations of categories and types, %s."
msgid "The actual value of the attribute, enter data about the value based on what is valid for the chosen attribute type. For example, for an attribute of type ip-src (source IP address), 11.11.11.11 would be a valid value. For more information on types and values, %s."
msgid "This option allows the attribute to be used as an IDS signature when exporting the NIDS data, unless it is being overruled by the white-list. For more information about the whitelist, head over to the %s section."
msgid "If there are several attributes of the same type to enter (such as a list of IP addresses, it is possible to enter them all into the same value-field, separated by a line break between each line. This will allow the system to create separate lines for the each attribute."
msgid "Templates allow users to rapidly populate events of a specific type by filling out a series of pre-defined fields. Users with template creation privileges can create new templates for their organisations or for all organisations on their instance. If you are interested in template creation, please refer to the templating section.<br />\n"
"For users trying to populate an event, after clicking on the populate from template button, you'll be presented with a list of all currently accessible templates. Pick the one that best describes the event that you are creating."
msgid "Once you have chosen a template, you'll be presented with the actual form contained within. Make sure you fill out as many fields as possible with the mandatory fields - marked by a star in a bracket such as this: (*) - are filled out.<br />\n"
"Templates are devided into sections, with each section having a title and a description in addition to a series of fields. Each field can be an attribute or a file attachment field. An attribute field has the following components"
msgid "The value(s) that are valid for the field. In the case of several types being shown here, you can enter value(s) matching any one of the types, or in the case of a batch import field, any mixture of the given types."
msgid "This field can either be a single line textfield or a multi-line text area. For the former, enter a single value of the above indicated type, whilst for the latter you cna paste a list of values separated by line-breaks."
msgid "If you have a list of indicators that you would like to quickly generate attributes out of then the Free-text import tool is just what you need. Simply paste a list of indicators (separated by line-breaks into this tool)."
msgid "Since there are several category / type combinations that can be valid for a lot of values, MISP will suggest the most common settings. You can alter the category / type / IDS fields manually if you disagree with the results. The options will be restricted to valid category/type combinations for the value that you have entered."
msgid "If you would like to create and maintain an event with a set of indicators that receives removals and additions over time, then the attribute replace tool might make this task easier for you."
msgid "Simply select the desired category / type combination, choose whether the attributes should be marked for IDS exports and paste the new list of indicators into the textarea. Attributes of the same category/type that are present in the event but not the new list will be removed, values in the pasted list that do not yet exist as attributes will be created as attributes and values that already have matching attributes will be left untouched."
msgid "You can also upload attachments, such as the malware itself, report files from external analysis or simply artifacts dropped by the malware. Clicking on the add attachment button brings up a form that allows you to quickly attach a file to the event. The following fields need to be filled out"
msgid "Point the uploader to the file you want to upload. Make sure to mark it as malware if the uploaded file is harmful, that way it will be neutralised."
msgid "By hitting browse, you can browse your file system and point the uploader to the file that you want to attach to the attribute. This will then be uploaded when the upload button is pushed."
msgid "This check-box marks the file as malware and as such it will be zipped and passworded, to protect the users of the system from accidentally downloading and executing the file. Make sure to tick this if you suspect that the filed is infected, before uploading it."
msgid "If you would like to propose a modification to an attribute, or to propose some additional attributes to the creating organisation, you can do this with the buttons that replace the add attribute field on the left and the edit icon on the right end of each listed attribute in the event view. The creating organisation of the event will be able to see any proposals and discard or accept the changes."
msgid "An attribute with a proposal attached will turn blue and the proposal itself will be grey. If there is a grey proposal without a blue attribute infront of it, it means that someone has proposed a new attribute"
msgid "If the organisation that has created the event is on another connected server, they will be able to accept the proposal once they initiate a pull and receive your proposal. After this they can republish the event, sending the altered attribute back to your instance."
msgid "It is also possible to attempt to import the data contained in a .ioc file, The import tool will attempt to gather as many IndicatorItems within nested logical operators as possible without breaking their validity. After the procedure is done, you'll be presented with a list of successfully created attributes and a list of failed IndicatorItems as well as a graph of the .ioc file."
msgid "You can also import the data from a ThreatConnect export csv file. The following columns are used by the import tool (and are thus mandatory fields to select during the export)"
msgid "The result will be a list of attributes that get added to the currently selected event, each of which will be marked with a comment that indicates that its origin being from a ThreatConnect import."
msgid "Once all the attributes and attachments that you want to include with the event are uploaded / set, it is time to finalise its creation by publishing the event (click on publish event in the event view). This will alert the eligible users of it (based on the private-controls of the event and its attributes/attachments and whether they have auto-alert turned on), push the event to instances that your instance connects to and propagate it further based on the distribution rules. It also readies the network related attributes for NIDS signature creation (through the NIDS signature export feature, for more information, go to the export section.)."
msgid "There is an alternate way of publishing an event without alerting any other users, by using the \"publish (no email)\" button. This should only be used for minor edits (such as correcting a typo)."
msgid "The MISP interface allows the user to have an overview over or to search for events and attributes of events that are already stored in the system in various ways."
msgid "On the left menu bar, the option \"List events\" will generate a list of the last 60 events. While the attributes themselves aren't shown in this view, the following pieces of information can be seen"
msgid "The event's ID number, assigned by the system when the event was first entered (or in the case of an event that was synchronized, when it was first copied over - more on synchronisation in chapter xy)"
msgid "The e-mail address of the event's reporter. This is not visible to regular users. Organisation administrators can see the e-mail addresses of their own organisation's users."
msgid "The controls that the user has to view or modify the event. The possible actions that are available (depending on user privileges - %s to find out more about privileges)"
msgid "Publishing an event will have several effects: The system will e-mail all eligible users that have auto-alert turned on (and having the needed privileges for the event, depending on its private classification) with a description of your newly published event, it will be flagged as published and it will be pushed to all eligible servers (to read more about synchronisation between servers, have a look at the %s)."
msgid "Clicking on the edit button will bring up the same screen as the one used for creating new events, with the exception that all fields come filled out with the data of the event that is being edited. The distribution of an event can only be edited if you are a user of the creating organisation of the event. For more information on this view, refer to the section on <a href=\"#create\">creating an event</a>."
msgid "It is also possible to filter the events shown by clicking on the small magnifying glass icons next to the field names and entering a filter term."
msgid "This view includes the basic information about an event, a link to related events, all attributes and attachments with tools to modify or delete them and extra functions for publishing the event or getting in touch with the event's reporter."
msgid "In order to avoid collisions between events and attributes (during for example a sync) a Uuid is assigned that uniquely identifies each of them."
msgid "The organisation that has originally created the event. The logo (if it exists on the server, alternatively a string) representing the organisation is also shown int he right upper corner."
msgid "Shows a list of the organisations that have contributed to the event via proposals. If you click any of the logos listed here, you'll get redirected to a filtered event history view, including only the changes made by the organisation."
msgid "A list of tags associated with the event. Clicking a tag will show a list of events with the same tag attached. The little cross next to each tag allows you to remove the tag from the event, whilst the '+' button allows you to assign a tag. For the latter two options to be visible, you have to have tagging permission."
msgid "This shows the distribution rules applied to this event, controlling whether only the creating organisation can see (Your organisation only) it or everyone on the instance (This community only). The two remaining settings allow the event to be propagated to organisations on remote connected instances."
msgid "A short description of the event itself. Make sure not to put information in here that could be used for correlation purposes and be better suited as an Attribute."
msgid "Whether the event has been published or not. Publishing allows the attributes of the event to be used for all eligible exports and it notifies users that have subscribed to the event alerts. Also, a publish initiates a push to all eligible instances."
msgid "The list of relations is shown on the right hand side of the general event information. Events can be related by having one or more attributes that are exact matches. For example, if two events both contain a source IP attribute of 11.11.11.11 then they are related. The list of events that are related the currently shown one, are listed under \"Related Events\", as links (titled the related event's date and ID number) to the events themselves."
msgid "You can control some of the data that is shown on this page using three toggles. The elements that can be disabled are the pivot threads, the attributes (and proposals) and the Discussions. You can collapse these elements and then expand them again using the same button."
msgid "While moving from event to event through the relation links (a process that we refer to as pivoting), you create a path that shows which events you have traversed. This path is reset by leaving the event view and navigating elsewhere in the application or by deleting the root pivot element."
msgid "Each event visited is represented by a bubble in the pivot thread graph, connected by lines that show how the user has arrived at the next connected event. It is possible to jump back to an earlier relation and pivot to another event through that, creating branches in the graph."
msgid "The currently selected event is coloured blue in the graph. If you would like to delete an element from the graph (including all of elements that branch off of it) just click on the small x within a pivot bubble. For a deletion to be possible the following conditions have to be met"
msgid "A list of all attributes and proposals attached to the event. The fields for each of them only differ in the available actions and the fact that for proposals to attributes all fields are blank that would stay unchanged if the proposal was accepted (for example, proposing a change to an attribute to turn the IDS flag on will have all fields apart from the IDS flag blank in the proposal. Here is a list of what each of the fields represents"
msgid "The category of the attribute or proposal. For a list of possible categories visit the section on <a href=\"%s/pages/display/doc/categories_and_types\">categories and types</a>."
msgid "The type of the attribute or proposal. For a list of possible categories visit the section on <a href=\"%s/pages/display/doc/categories_and_types\">categories and types</a>."
msgid "The value or value-pair of the attribute. This is the main payload of the attribute, which is described by the category and type columns. For certain types of attributes that are made up of value-pairs the two parts will be split by a pipe (|), such as for filename|md5. The value field(s) are used by the correlation engine to find relations between events. In value-pair attributes both values are correlated individually."
msgid "Attributes can have a contextual comment to further describe the attribute. These comments are not used for correlation and are purely informative."
msgid "Defines the distribution of the attribute individually. An attribute can have a different distribution level than the event. In any case, the lowest distribution level of the two is used."
msgid "The user can interact with the events through these buttons, which will be further described in the next portion of the guide as they differ for attributes and proposals."
msgid "Each gray line at the end of the list represents a Proposal to an event. These are proposals for a new attribute, mostly unrelated to any of the currently existing attributes. If the creator of the event accepts one of these a new attribute will be created."
msgid "Each attribute can have several edit proposals. These will be placed right below the attribute that the proposal affects and - as with the event proposals - is coloured grey. The original attribute's row is coloured blue if a proposal exists for it."
msgid "Each event has its own assigned discussion where users (that are eligible to see the event) can participate in an open discussion. The users are anonymised in the messages, all that other users will see is their user ID number and their organisation. To post a message on the Event Discussion, either use the reply button on a previous post or use the quickresponse field at the bottom of the page.\n"
msgid "The body of the post itself. This can also include automatically generated links to other events and threads as well as show quoted test in embedded bubbles. Editing an event will also append a post with a message indicating that it was edited together with the timestamp of the edit."
msgid "The e-mail address of the poster if he/she is from the organisation as the current user. Alternatively a generated sting is shown that includes the user ID of the user, so that his/her e-mail address could remain hidden whilst still being identifiable."
msgid "Edit, Delete and Reply. The first two of the three options are only available to the poster of the message or a site admin. Quoting a post will automatically include the original message in [quote] tags."
msgid "There are 5 posts visible on each event page, if there have been more messages posted, use the previous and next button to navigate through the thread. This will not reload the rest of the page."
msgid "Users can quote something by encapsulating it in [quote][/quote] tags, they can create a link to another event with the [event][/event] tags or to another discussion thread with [thread][/thread]."
msgid "Adding a post will take the user to a separate add Post page, something that can be a bit of an inconvenience. To avoid this, there is a quick post button, where users can add messages on the fly without having to reload the page. On top of the quick post field, 3 buttons allow users to generate quote, event and thread tags quickly."
msgid "View the logs of the event that show how the event has changed over time, including the contribution from other organisations in the form of proposals. There are two ways to get to this view, either by clicking on View Event History on the side menu of an event view, or by clicking on a contributing organisation's logo on the event view. The latter will show a restricted form of the logs, showing only Proposals created by the selected organisation. The fields shown in this view are as described as follows"
msgid "Each entry in the log happens during an action, such as the creation, modification or deletion of data and some special actions (such as accepting a proposal). This field shows which action caused the entry to be created."
msgid "As described above, a log entry is generated on certain actions. This field shows which type of data was affected that caused the log entry to be created (such as a change to the event, the creation of an attribute, the discarding of a proposal, etc)."
msgid "This is a short description of the change itself and it is not nearly as detailed as the information administrators get in the audit logs. However, for attributes and proposals the category / type and value of the created or edited attribute is shown."
msgid "Apart from having a list of all the events, it is also possible to get a list of all the stored attributes in the system by clicking on the list attributes button. The produced list of attributes will include the followings fields"
msgid "This is the ID number of the event that the attribute is tied to. If an event belongs to your organisation, then this field will be coloured red."
msgid "The category of the attribute, showing what the attribute describes (for example the malware's payload). For more information on categories, go to section xy"
msgid "A set of buttons that allow you to view the event that the attribute is tied to, to edit the attribute (using the same view as what is used to set up attributes, but filled out with the attribute's current data) and a delete button."
msgid "Apart from being able to list all events, it is also possible to search for data contained in the value field of an attribute, by clicking on the \"Search Attributes\" button."
msgid "This will bring up a form that lets you enter one or several search strings (separate search strings with line breaks) that will be compared to the values of all attributes, along with options to narrow down the search based on category and type. The entered search string has to be an exact match with (the sub-string of) a value. A second text field makes it possible to enter event IDs for events that should be excluded from the search (again, each line represents an event ID to be excluded). The third text field allows the user to restrict the results to attributes from certain organisations or to attributes not created by certain other organisations, using the above described syntax."
msgid "The list generated by the search will look exactly the same as listing all attributes, except that only the attributes that matched the search criteria will be listed (to find out more about the list attributes view, %s.). The search parameters will be shown above the produced list and the search terms will be highlighted."
msgid "Every event and attribute can easily be edited. First of all it is important to find the event or attribute that is to be edited, using any of the methods mentioned in the section on <a href=\"#browsing_events\">browsing past events</a>."
msgid "Once it is found, the edit button (whether it be under actions when events/attributes get listed or simply on the event view) will bring up the same screen as what is used to create the entry of the same type (for an event it would be the event screen as <a href=\"#create\">seen here</a>, for an attribute the attribute screen as <a href=\"#create_attribute\">described here</a>)."
msgid "Keep in mind that editing any event (either directly or indirectly through an attribute) will unpublish it, meaning that you'll have to publish it (through the event view) again once you are done."
msgid "As described earlier, users with tagging rights can arbitrarily tag events using tags chosen from a pool of available options. If you have tagging privileges and would like to create a new tag, navigate to Event Actions - Add Tag. You'll be presented with the following form"
msgid "You can choose a colour for the tag by clicking on the colour field and using the colour picker tool. Try to avoid having duplicate or similar looking colours to help avoid confusion."
msgid "Newer users can easily be overwhelmed by having to manually populate events with attributes without any guidance. What sort of information should go into the event? What should be the category and type of a C2 IP? Templates allow users to use simple forms to populate events."
msgid "Even though MISP ships with a few default templates, it is possible for users (with the appropriate templating privilege) to create new templates for their users or for all users of the instance. Let's look at how you can create a template."
msgid "You can attach tags to the template - an event populated using the template would automatically receive the tag(s). Add new tags using the + button. If you change your mind about a tag you can remove it with the cross next to the tag name."
msgid "Once the skeleton template is created, you can start populating the template with data. There are 3 types of elements that can be used during the creation of a template: attribute, file and text elements. Text elements divide the template into sections with an information field, followed by all of the attribute/file fields until a new text field is read. Don't worry about the order of the elements during creation, they can be re-arranged using drag & drop. Let's look at the 3 element types"
msgid "The type or complex type used for any attributes created using this template element. Complex types allow for several related types to be used on data entry. For example, a \"file\" complex type element allows for filenames and hashes."
msgid "The description of the section. Explain briefly to the user what the following attribute/file elements will be dealing with. There are several ways to split a template into sections, try to have ease of use in mind while creating it."
msgid "To get in touch with the reporter of a previously registered event, just find the event for which you would like to contact the reporter by either finding it on the list of events, by finding it through one of its attributes or by finding it through a related event."
msgid "Once the event is found and the event view opened, click the button titled \"Contact Reporter\". This will bring up a view where you can enter your message that is to be e-mailed to all members of the reporting organisation that subscribe to receiving such reports or the reporting user himself. Along with your message, the detailed information about the event in question will be included in the e-mail."
msgid "By default, the message will be sent to every member of the organisation that posted the event in the first place, but if you tick the check-box below the message field before sending the mail, only the person that reported the event will get e-mailed."
msgid "It is possible to quickly and conveniently export the data contained within the system using the automation features located in the main menu on the left (available to users with authentication key access only). There are various sets of data that can be exported, by using the authentication key provided by the system (also shown on the export page). If for whatever reason you would need to invalidate your current key and get a new one instead (for example due to the old one becoming compromised) just hit the reset link next to the authentication key in the export view or in your \"my profile\" view."
msgid "To find out about the various export formats and the usage within the automation functions, please read the page on <a href=\"%s/events/automation\">automation</a>."
msgid "For users that do not have authentication key access, an alternate export feature is available that relies on your interactive login to the site. To access these, just use the export menu button to the left and you'll be presented with a list of export options."
msgid "Depending on your server's configuration, you will be presented with one of two possible pages, depending on whether you have background processing enabled or not. (The setting on this instance is currently set to: <code>%s</code>)"
msgid "The page will list a set of export formats that you can immediately download as a file. Just click on the desired export format and MISP will start collecting all the data that you will receive in a file. Keep in mind that this can be a lengthy process. To avoid having to wait, consult with your instance's site administrator about enabling the background processing."
msgid "Use the export features here to quickly download data in various formats"
msgstr ""
#: View/Pages/doc/using_the_system.ctp:372
msgid "If the background jobs are enabled, you'll be redirected to a different version of the export page. Here you will see a table with all of the major export formats and the current status of the cached export files. Keep in mind that these are generated on an organisation by organisation basis, so even though others have generated newer export caches your organisation may have an outdated cache. You can simply issue a generate command (by clicking the \"Generate\" button) on the desired export type and the background workers will start fetching and assembling your cache. A progress bar will show the progress of the export process."
msgid "Once done, you can click \"Download\" to download the freshly generated cache file. If the cache is already up to date from before, then you don't have to regenerate the cache, just click on the \"download\" button."
msgid "You may have noticed that the TEXT export only has a generate button - this is because TEXT exports are made up of a lot of types of exports, all of which get generated together. To download any of these files, just click on any of the attribute types at the bottom of the table."
msgid "This compares the cache generation date to the last timestamp when an event was updated and lets you know whether the cache is outdated or not."
msgid "Apart from the options offered by the export pages, it's also possible to export all events involved in a search attribute result table, by using the \"Download results as XML\" button on the left menu bar."
msgid "Each event's view has its own export feature, both as an XML export and as a .ioc file. To reach these features, just navigate to an event and use the appropriate buttons on the right side."
msgid "Apart from being a self contained repository of attacks/malware, one of the main features of MISP is its ability to connect to other instances and share (parts of) its information. The following options allow you to set up and maintain such connections."
msgid "In order to share data with a remote server via pushes and pulls, you need to request a valid authentication key from the hosting organisation of the remote instance. When clicking on List Servers and then on New Server, a form comes up that needs to be filled out in order for your instance to connect to it. The following fields need to be filled out"
msgid "Make sure that you enter the authentication key that you have been given by the hosting organisation of the remote instance, instead of the one you have gotten from this one."
msgid "The organisation that runs the remote server. It is very impoportant that this setting is filled out exactly as the organisation name set up in the bootstrap file of the remote instance."
msgid "If the instance that you want to connect to has their entire own certificate chain, you can use this to import a .pem file with it and override CakePHP's standard root CA file."
msgid "If you are an administrator</b>, trying to allow another instance to connect to your own, it is vital that two rules are followed when setting up a synchronisation account"
msgid "Both the sync user and the organisation setting in your instance's Config/bootstrap.php file have to match the organisation identifier of the hosting organisation."
msgid "If you ever need to change the data about the linked servers or remove any connections, you have the following options to view and manipulate the server connections, when clicking on List Servers: (you will be able to see a list of all servers that your server connects to, including the base address, the organisation running the server the last pushed and pulled event IDs and the control buttons.)."
msgid "By clicking edit a view, <a href=#new_server>that is identical to the new instance view</a>, is loaded, with all the current information of the instance pre-entered."
msgid " By clicking this button, all events that are eligible to be pushed on the instance you are on will start to be pushed to the remote instance. Events and attributes that exist on the far end will be updated."
msgid "By clicking this button, all events that are set to be pull-able or full access on the remote server will be copied to this instance. Existing events will not be updated."
msgid "The platform is also <a href=\"http://en.wikipedia.org/wiki/Representational_state_transfer\">RESTfull</a>, so this means that you can use structured format (XML or JSON) to access Events data."
msgid "You can set this instance up as an internal instance by checking the checkbox below. This means that any synchronisation between this instance and the remote will not be automatically degraded as it would in a normal synchronisation scenario. Please make sure that you own both instances and that you are OK with this otherwise dangerous change."
msgstr ""
#: View/Servers/add.ctp:19
#: View/Servers/edit.ctp:19
msgid "Internal instance"
msgstr ""
#: View/Servers/add.ctp:29
msgid "Information about the organisation that will receive the events, typically the remote instance's host organisation."
msgid "You can also upload a certificate file if the instance you are trying to connect to has its own signing authority. (*.pem)"
msgstr ""
#: View/Servers/edit.ctp:16
msgid "You can set this instance up as an internal instance by checking the checkbox below. This means that any synchronisation between this instance and the remote will not be automatically degraded as it would in a normal synchronisation scenario. Please make sure that you own both instances and that you are OK with this otherwise dangerous change. This also requires that the current instance's host organisation and the remote sync organisation are the same."
msgid "Internal instance that ignores distribution level degradation *WARNING: Only use this setting if you have several internal instances and the sync link is to an internal extension of the current MISP community*"
msgid "Active sharing groups can be selected by users of the local instance when creating events. Generally, sharing groups received through synchronisation will have this disabled until manually enabled."
msgstr ""
#: View/SharingGroups/add.ctp:19
#: View/SharingGroups/edit.ctp:19
msgid "Make the sharing group selectable (active)"
msgstr ""
#: View/SharingGroups/add.ctp:21;38;59
#: View/SharingGroups/edit.ctp:21;38;67
msgid "Next page"
msgstr ""
#: View/SharingGroups/add.ctp:25
#: View/SharingGroups/edit.ctp:25
msgid "Add local organisation(s) to the sharing group"
msgstr ""
#: View/SharingGroups/add.ctp:25
#: View/SharingGroups/edit.ctp:25
msgid "Add local organisation"
msgstr ""
#: View/SharingGroups/add.ctp:26
#: View/SharingGroups/edit.ctp:26
msgid "Add remote organisations to the sharing group"
msgstr ""
#: View/SharingGroups/add.ctp:26
#: View/SharingGroups/edit.ctp:26
msgid "Add remote organisation"
msgstr ""
#: View/SharingGroups/add.ctp:33
#: View/SharingGroups/edit.ctp:33
#: View/SharingGroups/view.ctp:44
msgid "Extend"
msgstr ""
#: View/SharingGroups/add.ctp:37;58;74
#: View/SharingGroups/edit.ctp:37;66;82
msgid "Previous page"
msgstr ""
#: View/SharingGroups/add.ctp:42
#: View/SharingGroups/edit.ctp:50
msgid "Enable roaming mode for this sharing group. Roaming mode will allow the sharing group to be passed to any instance where the remote recipient is contained in the organisation list. It is preferred to list the recipient instances instead."
msgstr ""
#: View/SharingGroups/add.ctp:43
#: View/SharingGroups/edit.ctp:51
msgid "<b>Enable roaming mode</b> for this sharing group (pass the event to any connected instance where the sync connection is tied to an organisation contained in the SG organisation list)."
msgstr ""
#: View/SharingGroups/add.ctp:47
#: View/SharingGroups/edit.ctp:55
msgid "Add instance"
msgstr ""
#: View/SharingGroups/add.ctp:53
#: View/SharingGroups/edit.ctp:61
#: View/SharingGroups/view.ctp:69
msgid "All orgs"
msgstr ""
#: View/SharingGroups/add.ctp:63
msgid "<span class=\"bold\">General: </span>You are about to create the <span id=\"summarytitle\" class=\"red bold\"></span> sharing group, which is intended to be releasable to <span id=\"summaryreleasable\" class=\"red bold\"></span>."
msgstr ""
#: View/SharingGroups/add.ctp:64
msgid "Local organisations: </span>It will be visible to <span id=\"summarylocal\" class=\"red bold\"></span>, from which <span id=\"summarylocalextend\" class=\"red bold\"></span> can extend the sharing group."
msgstr ""
#: View/SharingGroups/add.ctp:65
msgid "External organisations: </span>It will also be visible to <span id=\"summaryexternal\" class=\"red bold\"></span>, out of which <span id=\"summaryexternalextend\" class=\"red bold\"></span> can extend the sharing group."
msgstr ""
#: View/SharingGroups/add.ctp:66
msgid "<span class=\"bold\">Synchronisation: </span>Furthermore, events are automatically pushed to: <span id=\"summaryservers\" class=\"red bold\"></span>"
msgstr ""
#: View/SharingGroups/add.ctp:67
#: View/SharingGroups/edit.ctp:75
msgid "You can edit this information by going back to one of the previous pages, or if you agree with the above mentioned information, click Submit to create the Sharing group."
msgstr ""
#: View/SharingGroups/add.ctp:75
#: View/SharingGroups/edit.ctp:83
msgid "Submit and create sharing group"
msgstr ""
#: View/SharingGroups/add.ctp:95
msgid "Local instance"
msgstr ""
#: View/SharingGroups/edit.ctp:71
msgid "<span class=\"bold\">General: </span>You are about to create the <span id=\"summarytitle\" class=\"red bold\"></span> sharing group, which is intended to be releasable to <span id=\"summaryreleasable\" class=\"red bold\"></span>. </p>\n"
"\t\t\t\t<p id=\"localText\"><span class=\"bold\">Local organisations: </span>It will be visible to <span id=\"summarylocal\" class=\"red bold\"></span>, from which <span id=\"summarylocalextend\" class=\"red bold\"></span> can extend the sharing group. </p>\n"
"\t\t\t\t<p id=\"externalText\"><span class=\"bold\">External organisations: </span>It will also be visible to <span id=\"summaryexternal\" class=\"red bold\"></span>, out of which <span id=\"summaryexternalextend\" class=\"red bold\"></span> can extend the sharing group."
msgstr ""
#: View/SharingGroups/edit.ctp:74
msgid "Synchronisation: </span>Furthermore, events are automatically pushed to: <span id=\"summaryservers\" class=\"red bold\"></span>"
msgid "Here you can schedule pre-defined tasks that will be executed every x hours. You can alter the date and time of the next scheduled execution and the frequency at which it will be repeated (expressed in hours). If you set the frequency to 0 then the task will not be repeated. To change and of the above mentioned settings just click on the appropriate field and hit update all when you are done editing the scheduled tasks."
msgid "Warning: Scheduled tasks come with a lot of caveats and little in regards of customisations / granularity. You can instead simply create cron jobs out of the console commands as described here: "
msgid "Are you sure you want to delete Taxonomy #<?php echo h($id); ?>?<br /> Associated tags will not be removed. You can reload the taxonomy at any time by updating your taxonomies."
msgid "Some categories can use complex types. A complex type can define attributes that can be described by various different types, the system will parse the user's entry and determine the most suitable type for the found attributes. The list of valid types for the chosen complex type is shown below."
msgid "Below you can see the attributes that are to be created based on the data that you have entered into the template. If you are satisfied with the result, click \"Finalise\". Otherwise, click \"Modify\"."
msgid "Messaging - here's a quick guide on how this feature works"
msgstr ""
#: View/Users/admin_email.ctp:7
msgid "You can use this view to send messages to your current or future users or send them a temporary password."
msgstr ""
#: View/Users/admin_email.ctp:9
msgid "When adding a new user to the system, or when you want to manually reset the password for a user, just use the \"Send temporary password\" setting."
msgstr ""
#: View/Users/admin_email.ctp:10
msgid "After selecting the action, choose who the target of the e-mails should be (all users, a single user or a user not yet in the system)."
msgstr ""
#: View/Users/admin_email.ctp:11
msgid "You can then specify (if eligible) what the e-mail address of the target is (for existing users you can choose from a dropdown menu)."
msgstr ""
#: View/Users/admin_email.ctp:12
msgid "In the case of a new user, you can specify the future user's GnuPG key, to send his/her new key in an encrypted e-mail."
msgstr ""
#: View/Users/admin_email.ctp:13
msgid "The system will automatically generate a message for you, but it is also possible to write a custom message if you tick the check-box,\n"
"\t\t\t\t\t\tbut don't worry about assigning a temporary password manually, the system will do that for you, right after your custom message."
msgid "WARNING: This user does not have an encryption key set. The security posture of this instance allows for the sending of clear-text e-mails, so this is what will happen if you proceed."
msgstr ""
#: View/Users/admin_quick_email.ctp:7
msgid "%s key found for user, the e-mail will be sent encrypted using this key."
msgstr ""
#: View/Users/admin_view.ctp:35
#: View/Users/view.ctp:29
msgid "Contactalert"
msgstr ""
#: View/Users/admin_view.ctp:46
msgid "Invited By"
msgstr ""
#: View/Users/admin_view.ctp:51
msgid "Org admin"
msgstr ""
#: View/Users/admin_view.ctp:74
#: View/Users/view.ctp:67
msgid "GnuPG fingerprint"
msgstr ""
#: View/Users/admin_view.ctp:80
#: View/Users/view.ctp:73
msgid "GnuPG status"
msgstr ""
#: View/Users/admin_view.ctp:90
#: View/Users/view.ctp:83
msgid "SMIME Public certificate"
msgstr ""
#: View/Users/admin_view.ctp:95
msgid "Nids Sid"
msgstr ""
#: View/Users/admin_view.ctp:110
msgid "Password change"
msgstr ""
#: View/Users/check_and_correct_pgps.ctp:2
msgid "Failed GnuPGs?"
msgstr ""
#: View/Users/check_and_correct_pgps.ctp:4
msgid "No failed composites"
msgstr ""
#: View/Users/edit.ctp:27
msgid "SMIME Public certificate (PEM format)"
msgstr ""
#: View/Users/login.ctp:37;44
msgid "Login"
msgstr ""
#: View/Users/statistics.ctp:8
#: View/Users/statistics_data.ctp:11
msgid "Some statistics about this instance. The changes since the beginning of this month are noted in brackets wherever applicable"
msgstr ""
#: View/Users/statistics.ctp:21
#: View/Users/statistics_data.ctp:26
msgid "Correlations found"
msgstr ""
#: View/Users/statistics.ctp:23
#: View/Users/statistics_data.ctp:28
msgid "Proposals active"
msgstr ""
#: View/Users/statistics.ctp:29
#: View/Users/statistics_data.ctp:34
msgid "Discussion threads"
msgstr ""
#: View/Users/statistics.ctp:34
#: View/Users/statistics_data.ctp:39
msgid "Discussion posts"
msgstr ""
#: View/Users/statistics.ctp:43
#: View/Users/statistics_data.ctp:48
msgid "A heatmap showing user activity for each day during this month and the 4 months that preceded it. Use the buttons below to only show the heatmap of a specific organisation."
msgstr ""
#: View/Users/statistics.ctp:60
#: View/Users/statistics_data.ctp:65
msgid "Go left"
msgstr ""
#: View/Users/statistics.ctp:66
#: View/Users/statistics_data.ctp:71
msgid "Go right"
msgstr ""
#: View/Users/statistics.ctp:113
#: View/Users/statistics_data.ctp:118
msgid "The above graph will not work correctly in Compatibility mode. Please make sure that it is disabled in your Internet Explorer settings."
msgstr ""
#: View/Users/statistics.ctp:117
#: View/Users/statistics_data.ctp:122
msgid "The above graph will not work correctly on Internet Explorer 9.0 and earlier. Please download Chrome, Firefox or upgrade to a newer version of Internet Explorer."
msgid "WARNING: This user does not have an encryption key set. The security posture of this instance allows for the sending of clear text e-mails, so this is what will happen if you proceed."
msgid "Are you sure you want to delete Warninglist #%s<br /> Associated tags will not be removed. You can reload the warninglist at any time by updating your warninglists."
msgstr ""
#: View/Whitelists/admin_add.ctp:4
msgid "Add Signature Whitelist"
msgstr ""
#: View/Whitelists/admin_edit.ctp:4
msgid "Edit Signature Whitelist"
msgstr ""
#: View/Whitelists/admin_index.ctp:3
#: View/Whitelists/index.ctp:3
msgid "Regex entries (in the standard php regex /{regex}/{modifier} format) entered below will restrict matching attributes from being included in the IDS flag sensitive exports (such as NIDS exports)."
msgid "Colour has to be in the RGB format (#FFFFFF)"
msgstr ""
#: Model/TemplateElementAttribute.php:validation for field category
#: Model/TemplateElementFile.php:validation for field category
msgid "Please choose a category."
msgstr ""
#: Model/TemplateElementAttribute.php:validation for field type
msgid "Please choose a type."
msgstr ""
#: Model/TemplateElementFile.php:validation for field name
#: Model/TemplateElementText.php:validation for field name
msgid "Please enter a Name"
msgstr ""
#: Model/TemplateElementFile.php:validation for field description
msgid "Please enter a Description"
msgstr ""
#: Model/TemplateElementText.php:validation for field text
msgid "Please fill out the text field"
msgstr ""
#: Model/User.php:validation for field password
msgid "Password length requirement not met."
msgstr ""
#: Model/User.php:validation for field password
msgid "Password complexity requirement not met."
msgstr ""
#: Model/User.php:validation for field password
msgid "Please re-enter your password twice so that the values match."
msgstr ""
#: Model/User.php:validation for field org_id
msgid "The organisation ID has to be a numeric value."
msgstr ""
#: Model/User.php:validation for field email
msgid "Please enter a valid email address."
msgstr ""
#: Model/User.php:validation for field email
msgid "An account with this email address already exists."
msgstr ""
#: Model/User.php:validation for field gpgkey
msgid "GnuPG key not valid, please enter a valid key."
msgstr ""
#: Model/User.php:validation for field certif_public
msgid "Certificate not valid, please enter a valid certificate (x509)."
msgstr ""
#: Model/User.php:validation for field nids_sid
msgid "A SID should be an integer."
msgstr ""
#: Model/Whitelist.php:validation for field name
msgid "Name not in the right format. Whitelist entries have to be enclosed by a valid php delimiter (which can be most non-alphanumeric / non-whitespace character). Format: \"/8.8.8.8/\" Please double check the name."