March 2021 - IntelMQ-users

IEP04: IntelMQ Data Format - Meta-Information
by Sebastian Waldbauer 22 Apr '21

22 Apr '21

Dear IntelMQ Developers and Users, nowadays security incidents are more important than 10 years ago. As IntelMQ can be used as core element for automated security incident handling, we would like to provide a way to share information with other intelmq instances. This proposal is also an alternative to IEP03 insofar as solving the "multiple values" is possible by using UUIDs so "link" related events in a backwards-compatible manner. If you're interested, please let us know, so we could organize a hackathon for further discussions about the specification of the meta-information. Previously this idea was discussed in [0] and [1]. [0] https://github.com/certtools/intelmq/blob/version-3.0-ideas/docs/architectu… [1] https://github.com/certtools/intelmq/issues/1521 # IEP04: Internal Data Format: Meta Information and Data Exchange To ease data exchange between two or more IntelMQ instances, adding some meta-information to the events can make this sharing easier in certain regards. "Linking" events could be based on the same theory as `git` using it - with parent hashes ( we would call it UUID ). ### TL;DR Communication between one or more IntelMQ instances & exchange data with a backwards-compatible format. P2P or centralized architecture is a big topic, which has to be discussed after the format is being set. ### Why is metadata important? Short and simple. To avoid race conditions & being able to discard/drop already processed events from other instances. ### Meta information Metadata is used to transfer some general data, which is not likely related to the event itself. It's more or less just an information to keep events clear & sortable. A message could look like: { "meta": { "version": 1, # protocol version, so we are allowed to fallback to old versions too "uuid": { current: "cert_at:aaaa-bbbb-cccc-dddd" # format to be decided parent: "cert_at:xxxx-yyyy-zzzz-ffff" # format to be discussed, if not set -> current is the parent uuid }, "type": "event", "format": "intelmq", # i. e. this field could contain "n6" or "idea", so the receiving component can decode on demand. }, "payload": { # normal intelmq data "source.ip": "127.0.0.1", "source.fqdn": "example.com", "raw": base64-blob } } Tell us your opinion about adding non-standardized meta-information fields ( i. e. RTIR ticket number, origin, other local contact informationen ... and so on ) #### The UUID For the UUID there are multiple options: 1. Generate a random 128 bit UUID 2. A list of entities, which dealt with this event already. For example if an event was passed on from cert-at to cert-ee, the field could look like `!cert-at!cert-ee`. A message sending loop can be detected if the own name is already in this field upon reception. 3. Using CyCat: `publisher-short-name:project-short-name:UUID`. For example: `cert-at:intelmq:72ddb00c-2d0a-4eea-b7ac-ae122b8e6c3b`, or `cert-pl:n6:f60c9fb9-81f9-4e0b-8a44-ea41326a15b3`. Some more research and discussion is required before the implementation of this option. Have a look at https://www.cycat.org/services/concept/ for more details. 4. A hash: A benefit using a hash is that we're able to recalculate them on every intelmq instance. ### Exporting events to other systems In IntelMQ 2.x the events only comprise of the "payload" and no meta information. For local storages like file output or databases, the meta information may not be relevant in some use-cases. So it needs to be possible to export events *without* meta information, which is also the backwards-compatible behaviour. The "type" field exists in the current format as "__type" in the flat payload structure. In the output bots there's currently a boolean parameter `message_with_type` to include the field `__type` in the "export". For optionally exporting meta-information like uuid or format, a similar logic could be used. ### How can data exchange work? This now depends on how IntelMQ instances can communicate, either Peer-to-peer or via a central data hub. Both of them do have pro's and con's. #### P2P ( Peer 2 Peer ) Decentralized network + Less downtimes: A downtime of one instance, does not affect the whole network + Better privacy: data is not shared to an unrelated instance + More secure: data can optionally be encrypted (key-exchange between instances?) + Decentralized and local maintenance ~ Network latency depends on server locations - Networking issues may occur How would data exchange looks like between two instances: 1) Instance A has events which should be relayed to Instance B & C, because they're not sure who the actually receiver should be 2) Instance A ensures all messages have a UUID 3) Instance A sends the data to Instance B & Instance C 4) Instance B checks the data & they're sure that the data should be for Instance C 5) Instance C receives data from Instance A & Instance B 6) Instance C checks the UUID, which is the same & drops the package from Instance B #### (Central) Data hub + Less maintenance: Is maintained by the hub administrator + Central data storage (reports can optionally be cached to be downloaded later) ~ Central data analysis (e.g. statistics) is possible ~ Network latency depends on server locations - point of failure: if network problems occur, no exchange is possible As already seen above, data exchange here would be less complicated. The sending may look like: 1) Instance A has events which should be relayed to Instance B (e.g. different country) 2) Instance A ensures all messages have a UUID 3) Instance A sends these messages to the data hub The reception side can look like: 1) Instance B connects to central instance 2) Instance B queries and downloads all available messages 3) Upon reception, all messages are de-duplicated based on the UUID: a) If the UUID is already known, discard the message b) If the UUID has not been seen before, continue with processing To sum up, both exchange variants are useful. More research is needed, i. e. a mixed infrastructure with centralized parts but can be decentralized too. However, this shall not be neither the purpose nor the aim of this IEP. -- // Sebastian Waldbauer <waldbauer(a)cert.at> - T: +43 1 5056416 7202 // CERT Austria - https://www.cert.at/ // Eine Initiative der nic.at GmbH - https://www.nic.at/ // Firmenbuchnummer 172568b, LG Salzburg

6 8

IEP03: IntelMQ Data Format - Multiple Values
by Sebastian Waldbauer 22 Apr '21

22 Apr '21

Dear IntelMQ Developers and Users, an evaluation of current challenges with the internal data format led to the idea of allowing multiple values for one field in IntelMQ 3.0 (scheduled for June 2021)[0]. The idea is described below, including various advantages and disadvantages. We appreciate your input, opinion and analysis of further implications on this idea. We plan to evaluate the feedback that emerged in two weeks. [0] https://github.com/certtools/intelmq/blob/version-3.0-ideas/docs/architectu… "The new IDF shall support (sorted) lists of IPs, domains, taxonomy categories, etc. By convention the most relevant item in such a list MUST be the first item in the sorted list." https://github.com/certtools/intelmq/blob/version-3.0-ideas/docs/architectu…: n6-system "Since the new IDF shall support multiple values, mapping to n6 should be rather easy." ## Use-cases ### Network information IntelMQ's format currently allows for *exactly one* value per field. For example, every event can have *one* `source.ip` and *one* `source.fqdn`. In some use-cases, multiple values can be useful, for example when querying DNS information. One domain (`source.fqdn`) can point to multiple IP addresses (`source.ip`). The other way round, multiple domains point to the same IP address is also very common. The use-case first appeared was that one IP address can be part of multiple Autonomous systems (`source.asn`).[1][2][3] See the examples below in section Format. [1]: "Multiple ASNs/networks per IP? #543" https://github.com/certtools/intelmq/issues/543 [2]: "BOT: DNS lookup #373" https://github.com/certtools/intelmq/issues/373 [3]: "reverse DNS: Only first record is used "https://github.com/certtools/intelmq/issues/877 ### Classification Another use-case is to use multiple classifications.[5] For example, if a website was hacked and used for a phishing page, it can be assigned two classifications: For the hacking: Taxonomy: information-content-security, type: unauthorised-modification-of-information For the phishing page: Taxonomy: fraud, type: phishing Another example are reachable networks services, which should not be accessible by the internet. Shadowserver provides a lot of this data. Open XDMCP instances are both DDoS amplifiers and Potentially unwanted accessible systems. Therefore both classifications apply: Taxonomy: vulnerable, type: ddos-amplifier Taxonomy: vulnerable, type: potentially-unwanted-accessible-system A list of all fields on the RSIT can be found in the RSIT repository[6] [5]: https://github.com/enisaeu/Reference-Security-Incident-Taxonomy-Task-Force/… [6]: https://github.com/enisaeu/Reference-Security-Incident-Taxonomy-Task-Force/… ## Format Some examples: {"source.ip": ["192.0.43.8"], "source.asn": [16876, 40528]} {"source.ip": ["10.0.0.1", "10.0.0.2"], "source.url": ["http://example.com/", "http://example.net"]} {"classification.taxonomy": ["information-content-security", "fraud"], "classification.type": ["unauthorised-modification-of-information", "phishing"], "source.url": ["http://example.com/"], "source.ip": ["10.0.0.1", "10.0.0.2"]} In the bots' code multiple values need to be taken car of. For example, instead of: ip_addr = event["source.ip"] # do stuff it is necessary to loop over the values: for ip_addr in event["source.ip"]: # do stuff This logic is required for *all* fields which can have multiple values, therefore nested loops may be necessary. Everything which processes IntelMQ data needs to be adapted, including data bases. See the "Disadvantages" section below. ### Optional back-conversion ("value-explosion") One variant/option of this IEP is to create a conversion layer from the new multi-value format to the old one-value format by creating multiple events with only one value per field. Using this conversion, compatibility with external components can be kept, while the advantages only exist inside the IntelMQ core (ie. the bots). Examples: {"source.ip": ["127.0.0.1", "127.0.0.2"], "source.fqdn": ["example.com"]} -> {"source.ip": "127.0.0.1", "source.fqdn": ["example.com"]}, {"source.ip": "127.0.0.2", "source.fqdn": ["example.com"]} {"source.ip": ["127.0.0.1", "127.0.0.2"], "source.fqdn": ["example.com", "example.org"]} -> {"source.ip": "127.0.0.1", "source.fqdn": "example.com"}, {"source.ip": "127.0.0.1", "source.fqdn": "example.org"}, {"source.ip": "127.0.0.2", "source.fqdn": "example.com"}, {"source.ip": "127.0.0.2", "source.fqdn": "example.org"} ### What will change? We'll change the behaviour of the current IntelMQ internal parsing process, i. e. you'll be able to add multiple IP addresses to on field, which will be handled as multiple events, but merged into one event. This will allow us to combine i. e. a domain with multiple IP addresses to one event. ### Advantages Supporting multiple values allows us to add multiple IP addresses to one event. As opposed to using multiple events with nearly similar data, the multiple-value approach reduces data duplication and has less overhead, while on the other hand the complexity increases. If multiple events would be used instead, related events would need to be linked together by other means (see section Alternative below). ### Disadvantages (breaking behaviour) The complexity in IntelMQ and all linked components increases without doubt. All components dealing with the IntelMQ-data need to be adapted to deal with multiple values. This includes all bots, but IntelMQ administrators need to adapt their configurations (e.g. filters, etc.) as well. Without the explosion-variant, all connected databases need to be adapted (e.g. PostgreSQL, SQLite, Elastic, MongoDB etc.) additionally and all software which is processing data from IntelMQ need to be adapted. PostgreSQL support arrays for columns, but the scheme conversion can be complex and resource-hungry. IntelMQ followed the KISS ("keep it simple, stupid")[4] principle from its beginning. It is disputable if multiple values breaks with this principle. [4]: https://en.wikipedia.org/wiki/KISS_principle ## Alternatives An alternative to using multiple values per field is to set unique identifiers (e.g. UUID) per event and let events with the same origin have the same "parent" identifier. This way, related events can be linked and compatibility is easier. Relating the events to each other requires extra steps although, but keeps the KISS principle. This approach will be described in IEP04. To solve the use-case of multiple classifications per event, the primary and most important classification can be used instead of multiple ones. A possible solution for the classification use-case above would be to some sort of tagging - in short "tags". I. e. { "source.ip": ["192.0.43.8"], "source.asn": [16876, 40528], "tags": ["ddos-amplifier", "info-disclosure", "mirai-botnet"] } ## Other IoC processing formats For reference, we describe the formats of other IoC-processing systems similar to IntelMQ. Both formats, IDEA and n6 do support multiple values in different kinds. If you know of other similar formats supporting multiple values, please speak up! ### "IDEA" The IDEA-format, used by CESNET-developed Warden, supports multiple values for some fields. But the data format structure differs clearly from IntelMQ's, as you can see in the example below. The classification is defined per address and network ranges are possible as addresses, what is not supported in IntelMQ. IDEA was designed from scratch to overcome disadvantages of Warden's previous data format. Example: "Source": [ { "Type": ["Phishing"], "IP4": ["192.168.0.2-192.168.0.5", "192.168.0.10/25"], "IP6": ["2001:0db8:0000:0000:0000:ff00:0042::/112"], "Hostname": ["example.com"], "URL": ["http://example.com/cgi-bin/killemall"], "Proto": ["tcp", "http"], "AttachHand": ["att1"], "Netname": ["ripe:IANA-CBLK-RESERVED1"] } ], "Target": [ { "Type": ["Backscatter", "OriginSpam"], "Email": ["innocent(a)example.com"], "Spoofed": true }, { "IP4": ["10.2.2.0/24"], "Anonymised": true } ] Upstream documentation: https://idea.cesnet.cz/en/index https://warden.cesnet.cz/en/index ### n6 In the n6 format, the addr field is a list of arrays with `ip`, `asn`, `cc` and `dir` fields. `addr` is similar to IntelMQ's `source` namespace, but the size of `addr` is much lower and the "direction" of the address is given by a field inside the addr item. Example: [{"ipv6": "abcd::1", "cc": "PL", "asn": 12345, "dir": "dst"}] Upstream documentation: https://n6sdk.readthedocs.io/en/latest/tutorial.html#field-class-addressfie… https://n6sdk.readthedocs.io/en/latest/tutorial.html#field-class-extendedad… -- // Sebastian Waldbauer <waldbauer(a)cert.at> - T: +43 1 5056416 7202 // CERT Austria - https://www.cert.at/ // Eine Initiative der nic.at GmbH - https://www.nic.at/ // Firmenbuchnummer 172568b, LG Salzburg

3 4

Elasticsearch BOT error
by Soni, Drupad 30 Mar '21

30 Mar '21

Hi Team, We have integrated output for elastic search which resulting into error as below. We have installed Intelmq: 2.3.1 and Elasticsearch, Kibana: 7.12. As per suggestion from your team latest version of Elasticsearch and kibana works perfectly well with Intelmq latest version. Bot initialization failed. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/intelmq/lib/bot.py", line 164, in __init__ self.init() File "/usr/lib/python3/dist-packages/intelmq/bots/outputs/elasticsearch/output.py", line 58, in init raise MissingDependencyError('elasticsearch', version='>=5.0.0,<6.0.0') intelmq.lib.exceptions.MissingDependencyError: Could not load dependency 'elasticsearch', please install it with apt/yum/dnf/zypper (possibly named python3-elasticsearch) or pip3. Please note that this bot requires elasticsearch version >=5.0.0,<6.0.0! Regards, Drupad Soni KPMG - Cyber Security Embassy Golf Links Business Park, Pebble Beach, 'B' Block, 1st & 2nd Floor, Off Intermediate Ring Road Mobile : +91 8140283894 Know more about our Cyber Security Services https://home.kpmg.com/in/en/home/services/advisory/risk-consulting/it-advis… ********************************************************************** KPMG (in India) allows reasonable personal use of the e-mail system. Views and opinions expressed in these communications do not necessarily represent those of KPMG (in India). ******************************************************************************************************* DISCLAIMER The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you have received this communication in error, please address with the subject heading "Received in error," send to postmaster1(a)kpmg.com, then delete the e-mail and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any opinions or advice contained in this e-mail are subject to the terms and conditions expressed in the governing KPMG client engagement letter. Opinions, conclusions and other information in this e-mail and any attachments that do not relate to the official business of the firm are neither given nor endorsed by it. KPMG cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses. KPMG, an Indian partnership and a member firm of KPMG International Cooperative ("KPMG International"), a Swiss entity that serves as a coordinating entity for a network of independent firms operating under the KPMG name. KPMG International Cooperative (“KPMG International”) provides no services to clients. Each member firm of KPMG International Cooperative (“KPMG International”) is a legally distinct and separate entity and each describes itself as such. “Notwithstanding anything inconsistent contained in the meeting invite to which this acceptance pertains, this acceptance is restricted solely to confirming my availability for the proposed call and should not be construed in any manner as acceptance of any other terms or conditions. Specifically, nothing contained herein may be construed as an acceptance (or deemed acceptance) of any request or notification for recording of the call, which can be done only if it is based on my explicit and written consent and subject to the terms and conditions on which such consent has been granted” *******************************************************************************************************

2 2

Fwd: RE: Intelmq Stopped working
by Sebastian Wagner 30 Mar '21

30 Mar '21

Forwarding a held-back message, with the screenshot removed -------- Forwarded Message -------- Subject: RE: Intelmq Stopped working Date: Tue, 30 Mar 2021 07:23:02 +0000 From: Soni, Drupad <drupadsoni(a)kpmg.com> To: intelmq-users(a)lists.cert.at <intelmq-users(a)lists.cert.at> CC: Shah, Kunal <kunalshah3(a)kpmg.com>, Gupta, Anshul <anshulgupta9(a)kpmg.com>, Thakur, Richu <richuthakur(a)kpmg.com> Hi Team, Also, I am sharing apache2 logs. [Tue Mar 30 00:07:52.663070 2021] [mpm_event:notice] [pid 1428:tid 140542945885120] AH00489: Apache/2.4.29 (Ubuntu) mod_wsgi/4.5.17 Python/3.6 config$ [Tue Mar 30 00:07:52.663136 2021] [core:notice] [pid 1428:tid 140542945885120] AH00094: Command line: '/usr/sbin/apache2' [Tue Mar 30 00:07:54.162925 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] Loading config from /etc/intelmq/api-config.j$ [Tue Mar 30 00:07:54.809830 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] mod_wsgi (pid=18601): Exception occurred proc$ [Tue Mar 30 00:07:54.811024 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] Traceback (most recent call last):, referer: $ [Tue Mar 30 00:07:54.811137 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] File "/usr/lib/python3/dist-packages/intelm$ [Tue Mar 30 00:07:54.811164 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] return __hug_wsgi__(environ, start_respon$ [Tue Mar 30 00:07:54.811173 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] File "hug/api.py", line 500, in hug.api.Mod$ [Tue Mar 30 00:07:54.811182 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] File "hug/api.py", line 371, in hug.api.HTT$ [Tue Mar 30 00:07:54.811188 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] File "hug/api.py", line 638, in hug.api.API$ [Tue Mar 30 00:07:54.811195 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] File "/usr/lib/python3/dist-packages/intelm$ [Tue Mar 30 00:07:54.811199 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] intelmq_api.api.initialize_api(api_config$ [Tue Mar 30 00:07:54.811209 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] File "/usr/lib/python3/dist-packages/intelm$ [Tue Mar 30 00:07:54.811232 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] file_access.update_from_runctl(runner.get$ [Tue Mar 30 00:07:54.811243 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] File "/usr/lib/python3/dist-packages/intelm$ [Tue Mar 30 00:07:54.811251 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] return dict(json.load(self.debug(get_path$ [Tue Mar 30 00:07:54.811262 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] File "/usr/lib/python3/dist-packages/intelm$ [Tue Mar 30 00:07:54.811269 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] return self._run_json(args), referer: htt$ [Tue Mar 30 00:07:54.811280 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] File "/usr/lib/python3/dist-packages/intelm$ [Tue Mar 30 00:07:54.811295 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] completed = self._run_intelmq_ctl(["--typ$ [Tue Mar 30 00:07:54.811308 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] File "/usr/lib/python3/dist-packages/intelm$ [Tue Mar 30 00:07:54.811326 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] "command": shell_command_for_errors(comma$ [Tue Mar 30 00:07:54.811368 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] intelmq_api.runctl.IntelMQCtlError: Traceback$ [Tue Mar 30 00:07:54.811377 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] File "/usr/bin/intelmqctl", line 11, in <mo$ [Tue Mar 30 00:07:54.811382 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] load_entry_point('intelmq==2.3.1', 'conso$ [Tue Mar 30 00:07:54.811387 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] File "/usr/lib/python3/dist-packages/intelm$ [Tue Mar 30 00:07:54.811392 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] x = IntelMQController(interactive=True), $ [Tue Mar 30 00:07:54.811398 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] File "/usr/lib/python3/dist-packages/intelm$ [Tue Mar 30 00:07:54.811403 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] self.logging_level = self.parameters.logg$ [Tue Mar 30 00:07:54.811409 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] AttributeError: 'Parameters' object has no at$ [Tue Mar 30 00:07:54.811414 2021] [wsgi:error] [pid 18601:tid 140542679680768] [client 127.0.0.1:40320] , referer: http://localhost/intelmq-manager/c$ Regards, Drupad Soni *KPMG – Cyber Security* Embassy Golf Links Business Park, Pebble Beach, 'B' Block, 1st & 2nd Floor, Off Intermediate Ring Road Mobile : +91 8140283894 Know more about our *Cyber Security Services* https://home.kpmg.com/in/en/home/services/advisory/risk-consulting/it-advis… *From:* IntelMQ-users <intelmq-users-bounces(a)lists.cert.at> *On Behalf Of *Soni, Drupad via IntelMQ-users *Sent:* Tuesday, March 30, 2021 12:08 PM *To:* intelmq-users(a)lists.cert.at *Cc:* Shah, Kunal <kunalshah3(a)kpmg.com>; Gupta, Anshul <anshulgupta9(a)kpmg.com>; Thakur, Richu <richuthakur(a)kpmg.com> *Subject:* [IntelMQ-users] Intelmq Stopped working Hi Team, We started adding collectors to Intelmq. We did 20 collectors later we rebooted this machine as it was lagging. Now we are not able to login. Please guide us troubleshooting this. Regards, Drupad Soni *KPMG – Cyber Security* Embassy Golf Links Business Park, Pebble Beach, 'B' Block, 1st & 2nd Floor, Off Intermediate Ring Road Mobile : +91 8140283894 Know more about our *Cyber Security Services* https://home.kpmg.com/in/en/home/services/advisory/risk-consulting/it-advis… ------------------------------------------------------------------------ KPMG (in India) allows reasonable personal use of the e-mail system. Views and opinions expressed in these communications do not necessarily represent those of KPMG (in India). ******************************************************************************************************* DISCLAIMER The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you have received this communication in error, please address with the subject heading "Received in error," send to postmaster1(a)kpmg.com <mailto:postmaster1@kpmg.com>, then delete the e-mail and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any opinions or advice contained in this e-mail are subject to the terms and conditions expressed in the governing KPMG client engagement letter. Opinions, conclusions and other information in this e-mail and any attachments that do not relate to the official business of the firm are neither given nor endorsed by it. KPMG cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses. KPMG, an Indian partnership and a member firm of KPMG International Cooperative ("KPMG International"), a Swiss entity that serves as a coordinating entity for a network of independent firms operating under the KPMG name. KPMG International Cooperative (“KPMG International”) provides no services to clients. Each member firm of KPMG International Cooperative (“KPMG International”) is a legally distinct and separate entity and each describes itself as such. “Notwithstanding anything inconsistent contained in the meeting invite to which this acceptance pertains, this acceptance is restricted solely to confirming my availability for the proposed call and should not be construed in any manner as acceptance of any other terms or conditions. Specifically, nothing contained herein may be construed as an acceptance (or deemed acceptance) of any request or notification for recording of the call, which can be done only if it is based on my explicit and written consent and subject to the terms and conditions on which such consent has been granted” *******************************************************************************************************

2 1

Intelmq Stopped working
by Soni, Drupad 30 Mar '21

30 Mar '21

Hi Team, We started adding collectors to Intelmq. We did 20 collectors later we rebooted this machine as it was lagging. Now we are not able to login. Please guide us troubleshooting this. [cid:image001.png@01D7255C.F971E950] Regards, Drupad Soni KPMG - Cyber Security Embassy Golf Links Business Park, Pebble Beach, 'B' Block, 1st & 2nd Floor, Off Intermediate Ring Road Mobile : +91 8140283894 Know more about our Cyber Security Services https://home.kpmg.com/in/en/home/services/advisory/risk-consulting/it-advis… ********************************************************************** KPMG (in India) allows reasonable personal use of the e-mail system. Views and opinions expressed in these communications do not necessarily represent those of KPMG (in India). ******************************************************************************************************* DISCLAIMER The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you have received this communication in error, please address with the subject heading "Received in error," send to postmaster1(a)kpmg.com, then delete the e-mail and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any opinions or advice contained in this e-mail are subject to the terms and conditions expressed in the governing KPMG client engagement letter. Opinions, conclusions and other information in this e-mail and any attachments that do not relate to the official business of the firm are neither given nor endorsed by it. KPMG cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses. KPMG, an Indian partnership and a member firm of KPMG International Cooperative ("KPMG International"), a Swiss entity that serves as a coordinating entity for a network of independent firms operating under the KPMG name. KPMG International Cooperative (“KPMG International”) provides no services to clients. Each member firm of KPMG International Cooperative (“KPMG International”) is a legally distinct and separate entity and each describes itself as such. “Notwithstanding anything inconsistent contained in the meeting invite to which this acceptance pertains, this acceptance is restricted solely to confirming my availability for the proposed call and should not be construed in any manner as acceptance of any other terms or conditions. Specifically, nothing contained herein may be construed as an acceptance (or deemed acceptance) of any request or notification for recording of the call, which can be done only if it is based on my explicit and written consent and subject to the terms and conditions on which such consent has been granted” *******************************************************************************************************

3 3

IntelMQ & API & Manager 2.3.1
by Sebastian Wagner 25 Mar '21

25 Mar '21

Dear community, This IntelMQ version did not gain any major features and is a sole product maintenance release. It covers various minor error corrections in the IntelMQ software, and usability enhancements for the new API. Some notable changes are listed below. Thanks again to all contributors! The installation instructions: https://intelmq.readthedocs.io/en/maintenance/user/installation.html Upgrade instructions: https://intelmq.readthedocs.io/en/maintenance/user/upgrade.html All packages have been published to PyPI. The deb/rpm-repositories and dockerhub are following on Friday. I'm trying to summarize the changes here, the full changelogs are linked below. The Cymru CAP Parser has been adapted to the new format for events of the category "bruteforce" (PR#1795 by Sebastian Wagner, CERT.at, fixes 1794). The Shodan Parser now supports nested conversions, improved protocol detection and has a majorly extended parser mapping (PR#1821 by Mikk Markus Möll, CERT.EE). The feed documentation gained a missing description for the Shodan Country Stream (by Sebastian Wagner, CERT.at). On the documentation front, the ecosystem document received revised sections on intelmq-cb-mailgen and fody (PR#1792 by Bernhard Reiter, Intevation). A new section in the documentation summarizes hardware requirements (PR#1811 by Sebastian Wagner, CERT.at). Minor enhancements and adaptions in the tests. # IntelMQ API-related changes The IntelMQ API documentation now has more details on the required write permission for the session database file (PR#1798 by Birger Schacht, CERT.at, fixes intelmq-api#23). See https://intelmq.readthedocs.io/en/maintenance/user/intelmq-api.html Session database permission errors: Catch the exception in the code and add a hint to check the permissions of both the file and the directory (PR#25 by Birger Schacht, CERT.at, fixes #23). The tool `intelmqsetup`, which is part of the installation routine for manual IntelMQ installations, is now able to automatically create the required directory layout and file permissions for the IntelMQ API (PR#1787 by Sebastian Wagner, CERT.at, fixes #1783) and as well covers the webserver and sudoers configuration for IntelMQ API and IntelMQ Manager (PR#1805 by Sebastian Wagner, CERT.at, fixes #1803). # IntelMQ Manager-related changes The required authentication token in save-data request of the "Configuration" tab is now sent to the backend (PR#245 by Marcos Gonzalez, CNCSRD-DO, fixes #244). On two locations the link destinations have been fixed, they still linked to the old PHP-based backend URLs: "Clear Configuration" link destination (PR#249 by Sebastian Wagner, CERT.at, fixes #248) and link to configuration page of bot on the monitor page (PR#249 by Sebastian Wagner, CERT.at, fixes #248). # Full changelogs: IntelMQ: https://github.com/certtools/intelmq/releases/tag/2.3.1 IntelMQ API: https://github.com/certtools/intelmq-api/releases/tag/2.3.1 IntelMQ Manager: https://github.com/certtools/intelmq-manager/releases/tag/2.3.1 -- // Sebastian Wagner <wagner(a)cert.at> - T: +43 1 5056416 7201 // CERT Austria - https://www.cert.at/ // Eine Initiative der nic.at GmbH - https://www.nic.at/ // Firmenbuchnummer 172568b, LG Salzburg

1 0

Error accessing intelmq
by Soni, Drupad 19 Mar '21

19 Mar '21

Hi Team, While accessing http://localhost/Intelmq-manager/ I am receiving below error. Please guide in troubleshooting this. I have installed Intelmq using below commands: echo 'deb http://download.opensuse.org/repositories/home:/sebix:/intelmq/xUbuntu_18.0… /' | sudo tee /etc/apt/sources.list.d/home:sebix:intelmq.list curl -fsSL https://download.opensuse.org/repositories/home:sebix:intelmq/xUbuntu_18.04… | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/home_sebix_intelmq.gpg > /dev/null sudo apt-get -y update sudo apt-get -y install intelmq sudo apt-get -y install intelmq-manager sudo apt-get -y install Intelmq-api sudo apt-get -y update [cid:image001.png@01D71CA3.B2192BC0] Regards, Drupad Soni KPMG - Cyber Security Embassy Golf Links Business Park, Pebble Beach, 'B' Block, 1st & 2nd Floor, Off Intermediate Ring Road Mobile : +91 8140283894 Know more about our Cyber Security Services https://home.kpmg.com/in/en/home/services/advisory/risk-consulting/it-advis… ********************************************************************** KPMG (in India) allows reasonable personal use of the e-mail system. Views and opinions expressed in these communications do not necessarily represent those of KPMG (in India). ******************************************************************************************************* DISCLAIMER The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you have received this communication in error, please address with the subject heading "Received in error," send to postmaster1(a)kpmg.com, then delete the e-mail and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any opinions or advice contained in this e-mail are subject to the terms and conditions expressed in the governing KPMG client engagement letter. Opinions, conclusions and other information in this e-mail and any attachments that do not relate to the official business of the firm are neither given nor endorsed by it. KPMG cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses. KPMG, an Indian partnership and a member firm of KPMG International Cooperative ("KPMG International"), a Swiss entity that serves as a coordinating entity for a network of independent firms operating under the KPMG name. KPMG International Cooperative (“KPMG International”) provides no services to clients. Each member firm of KPMG International Cooperative (“KPMG International”) is a legally distinct and separate entity and each describes itself as such. “Notwithstanding anything inconsistent contained in the meeting invite to which this acceptance pertains, this acceptance is restricted solely to confirming my availability for the proposed call and should not be construed in any manner as acceptance of any other terms or conditions. Specifically, nothing contained herein may be construed as an acceptance (or deemed acceptance) of any request or notification for recording of the call, which can be done only if it is based on my explicit and written consent and subject to the terms and conditions on which such consent has been granted” *******************************************************************************************************

3 3

Intelmq login username and password
by Soni, Drupad 18 Mar '21

18 Mar '21

Hi Intelmq Team, We have successfully setup Intelmq but we are unable to login . Please help us out with default username and password. I have used intelmq:intelmq also intelmqadmin:intelmqadmin Please see below. [cid:image001.jpg@01D71A81.9E1B94B0] Regards, Drupad Soni KPMG - Cyber Security Embassy Golf Links Business Park, Pebble Beach, 'B' Block, 1st & 2nd Floor, Off Intermediate Ring Road Mobile : +91 8140283894 Know more about our Cyber Security Services https://home.kpmg.com/in/en/home/services/advisory/risk-consulting/it-advis… ********************************************************************** KPMG (in India) allows reasonable personal use of the e-mail system. Views and opinions expressed in these communications do not necessarily represent those of KPMG (in India). ******************************************************************************************************* DISCLAIMER The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you have received this communication in error, please address with the subject heading "Received in error," send to postmaster1(a)kpmg.com, then delete the e-mail and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any opinions or advice contained in this e-mail are subject to the terms and conditions expressed in the governing KPMG client engagement letter. Opinions, conclusions and other information in this e-mail and any attachments that do not relate to the official business of the firm are neither given nor endorsed by it. KPMG cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses. KPMG, an Indian partnership and a member firm of KPMG International Cooperative ("KPMG International"), a Swiss entity that serves as a coordinating entity for a network of independent firms operating under the KPMG name. KPMG International Cooperative (“KPMG International”) provides no services to clients. Each member firm of KPMG International Cooperative (“KPMG International”) is a legally distinct and separate entity and each describes itself as such. “Notwithstanding anything inconsistent contained in the meeting invite to which this acceptance pertains, this acceptance is restricted solely to confirming my availability for the proposed call and should not be construed in any manner as acceptance of any other terms or conditions. Specifically, nothing contained herein may be construed as an acceptance (or deemed acceptance) of any request or notification for recording of the call, which can be done only if it is based on my explicit and written consent and subject to the terms and conditions on which such consent has been granted” *******************************************************************************************************

3 24

Configurations in Intelmq
by Soni, Drupad 18 Mar '21

18 Mar '21

Hi Team, I have a query with the following below, where to store password file and with which extension? Also below it is mentioned on Intelmq-manager edit httpd.conf file. Where to do so? [cid:image001.png@01D71C08.A3E9E5D0] Regards, Drupad Soni KPMG - Cyber Security Embassy Golf Links Business Park, Pebble Beach, 'B' Block, 1st & 2nd Floor, Off Intermediate Ring Road Mobile : +91 8140283894 Know more about our Cyber Security Services https://home.kpmg.com/in/en/home/services/advisory/risk-consulting/it-advis… ********************************************************************** KPMG (in India) allows reasonable personal use of the e-mail system. Views and opinions expressed in these communications do not necessarily represent those of KPMG (in India). ******************************************************************************************************* DISCLAIMER The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you have received this communication in error, please address with the subject heading "Received in error," send to postmaster1(a)kpmg.com, then delete the e-mail and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any opinions or advice contained in this e-mail are subject to the terms and conditions expressed in the governing KPMG client engagement letter. Opinions, conclusions and other information in this e-mail and any attachments that do not relate to the official business of the firm are neither given nor endorsed by it. KPMG cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses. KPMG, an Indian partnership and a member firm of KPMG International Cooperative ("KPMG International"), a Swiss entity that serves as a coordinating entity for a network of independent firms operating under the KPMG name. KPMG International Cooperative (“KPMG International”) provides no services to clients. Each member firm of KPMG International Cooperative (“KPMG International”) is a legally distinct and separate entity and each describes itself as such. “Notwithstanding anything inconsistent contained in the meeting invite to which this acceptance pertains, this acceptance is restricted solely to confirming my availability for the proposed call and should not be construed in any manner as acceptance of any other terms or conditions. Specifically, nothing contained herein may be construed as an acceptance (or deemed acceptance) of any request or notification for recording of the call, which can be done only if it is based on my explicit and written consent and subject to the terms and conditions on which such consent has been granted” *******************************************************************************************************

2 2

Re: [IntelMQ-users] Dependency Resolution problem on CentOS 7
by Marco Teixeira 17 Mar '21

17 Mar '21

Hi there, Please ignore the previous email... i am now stuck at this: --> Finished Dependency Resolution Error: Package: python3-hug-2.6.1-4.4.noarch (home_sebix_intelmq) Requires: python3-falcon You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Regards, Marco -----Mensagem original----- De: Marco Teixeira Enviada: 16 de março de 2021 18:52 Para: intelmq-users(a)lists.cert.at Assunto: Dependency Resolution problem on CentOS 7 Hello, Can anyone help with the following dependencies error? Thank you Marco === [...] --> Finished Dependency Resolution Error: Package: python3-intelmq-2.3.0-1.1.noarch (home_sebix_intelmq) Requires: /bin/python3.6 Removing: python3-3.6.8-13.el7.x86_64 (@base) Not found Updated By: python3-3.6.8-18.el7.x86_64 (updates) Not found Error: Package: python3-pyasn-1.6.1-1.3.x86_64 (home_sebix_intelmq) Requires: /bin/python3.6 Removing: python3-3.6.8-13.el7.x86_64 (@base) Not found Updated By: python3-3.6.8-18.el7.x86_64 (updates) Not found Error: Package: python3-intelmq-api-2.3.0-1.1.noarch (home_sebix_intelmq) Requires: /bin/python3.6 Removing: python3-3.6.8-13.el7.x86_64 (@base) Not found Updated By: python3-3.6.8-18.el7.x86_64 (updates) Not found Error: Package: python3-hug-2.6.1-4.4.noarch (home_sebix_intelmq) Requires: /bin/python3.6 Removing: python3-3.6.8-13.el7.x86_64 (@base) Not found Updated By: python3-3.6.8-18.el7.x86_64 (updates) Not found Error: Package: python3-hug-2.6.1-4.4.noarch (home_sebix_intelmq) Requires: python3-falcon You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest === $ cat /etc/redhat-release CentOS Linux release 7.8.2003 (Core) ===

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

IntelMQ-users March 2021