Specifications

This is the specification for Open API of the the FIWARE Cybersecurity Generic Enabler. First will be presented the API of the Cybersecurity GE that is used between the server (Cyber inputs generation, scored attack paths engine and remediation calculation) and the visualization client. Then will be presented the part of the Cybersecurity GE that is concerned with managing groups of peers for privacy-preserving data sharing, or P2DS. P2DS is achieved through secure multiparty computation, or SMCP.

Introduction

The CyberSecurity GE Open API introduces three main concepts:

• Scored Attack Paths;
• Remediations;
• Privacy-Preserving Data Sharing.

Scored Attack Paths

The attack graph engine is a Topological Vulnerability Analyser (TVA) able to generate, from the output of Cyber Data Extraction (the parts related to the network topology and vulnerabilities of the information system) the attack graph regrouping all possible attack paths. This engine also combines the attack graph with the Common Vulnerability Scoring System (CVSS), to provide a quantitative analysis of individual vulnerabilities.

The main attack paths of the attack graph provided by the Attack Graph Engine are processed by a scoring function that computes a score for each attack path based on its business impact and probability of occurrence. The score basically represents the risk level.

Remediations

The remediation engine helps to mitigate the risks and to take efficient actions in accordance with the security policy by computing the different means to break the attack graph (so-called remediations) according to the AND/OR graph formalism and estimating a cost for each one. Once a security operator can actually select a specific attack path that he/she wants to prevent and get all the relevant alternatives of remediation.

Privacy-Preserving Data Sharing

The main issue is the following: when organisations are asked to share data about security, they are naturally reluctant to do so, because revealing this data may lead to loss of trust or it may reveal details of the organisation's business that a competitor could use to its advantage. On the other hand, sharing data could be mutually beneficial. For example, when an organisation is the victim of a denial-of-service attack, it is useful to know whether other organisations are also a victim. This is where privacy-preserving data sharing comes in.

The technology for P2DS, called SEPIA was developed as part of a PhD thesis at ETH Zurich.

In this API, there are several instances where a registration code is transported in the URL. This registration code is an authentication token; everyone with that authentication token can access the service. It is therefore a very, very good idea to use https on these calls, and probably https everywhere.

Terminology

Scored attack paths and remediations

The main terms used for the scored attack paths are:

• a vulnerability scanner automates the testing and discovery of services and known security weaknesses. For example, Nessus is a vulnerability scanner designed to automate the testing and discovery of known security issues.
• an attack graph is a directed graph containing all the attacks that are possible in an information system. It can be represented as a logical graph (AND/OR graph) describing the logical facts that are necessary to carry out an attack or as a topological graph describing which attacks can happen between hosts of the system. An attack graph is generally build thanks to the result of a vulnerability scanner.
• an attack path is an extract of an attack graph which focus an one/several/all ways to attack a specific target. Attack paths can be scored to be ranked and keep only the most important (likely or valuable) attack paths.
• a remediation is a way to prevent the execution of an attack path and protect its target. A remediation can be attached to an operational cost describing how it will cost effectively to an entreprise that wants to implement this remediation. Remediations can be, for example, the deployment of a firewall rule, of a Snort rule, or a patch.
• an IDMEF alert is a standardized alert that contains information about what has been detected, the sources of attack and targets of the attack. See https://www.ietf.org/rfc/rfc4765.txt for more information.

Privacy-Preserving Data Sharing

Let's say we have three organisations, called Domain 1, Domain 2, and Domain 3 in the graphic, that want to know the total number of attacks seen in the last 24 hours, with a granularity of five minutes. In mathematical terms, what these organisations want is x1 + x2 + x3, where x1, x2, and x3 are vectors with 24*60/5 = 288 elements, and they want to do this without revealing their own xi to any of the other domains. Here is how the three domains could use P2DS for their needs.

First, each domain provides an input peer. This is a service that is run by each domain, which knows the original, private xi from domain i.

Next, someone provides a number of privacy peers. These services can be run by anyone; they never have access to unencrypted data, so it doesn't matter who runs them. The only thing that matters is that the privacy peers are for the most part diligent, i.e., faithfully carry out their assigned task. The SEPIA protocol can tolerate a small number of malicious peers; only when more than this number of peers are malicious will the computation be deemed unsuccessful. The privacy peers execute a multi-round protocol in which they exchange encrypted information and perform computations on these encrypted values to get yet more encrypted values. No one learns the cleartext values of these encrypted vectors, not the privacy peers, not the domains.

But when the computation is finished, the end result becomes available in the clear and each domain can learn the value of x1 + x2 + x3. For example, Domain 1 learns the value of x1 + x2 + x3, but knows nothing about x2 or x3, except, trivially, their sum.

In our GE, the privacy peers are provided by the domains.

A final component of our contribution is the group manager. This is the service that knows which input peers and which privacy peers should cooperate in a computation, which keeps the peers' public key certificates, and which provides SEPIA configuration when it is time to start the computation. It does not have to be especially trusted (none of the data it has is particularly secret) but it must be authentic, in the sense that the data it keeps should be protected against unauthorised alteration.

There are a few caveats in using SEPIA:

• When there are only two input peers and they compute a sum, each peer can compute the contribution of the other peer through a simple subtraction: If I know x and x + y, I can compute y as (x + y) - x.
• In general, when there are n ≥ 3 input peers and n - 1 of them collude to defraud the remaining one, they can simply exchange their own input vectors through a side channel.
• In general, SEPIA is secure in what is known as the honest but curious adversary model, in which adversaries try to learn the contents of messages but will not actively try to disrupt the protocol.

Conformance

All the interfaces described by this specification are mandatory and must be implemented in order to be compliant with.

Common Payload Definition

PeerInfo

gid (optional, number)

The group to which this peer belongs.

lastStatus (optional, stopped = 3)

None

peerName (optional, string)

A descriptive name for the peer.

peerType (optional, privacy peer = 2)

None

publicKey (optional, string)

The peer's public key.

url (optional, string)

The URL at which to contact the peer.

DataSets

data (optional, list)

List of semicolon seperated integers

peerName (optional, string)

Name of the peer

Group

gid (optional, number)

The group's identifier, guaranteed to be unique for this group manager.

name (optional, string)

A descriptive name of a group

DataSet

data (optional, string)

semicolon seperated integers

peerName (optional, string)

Name of the peer to add the data set for

GroupName

name (optional, string)

Name of the group

GroupConfigurationInfo

field (optional, string) - Field value for the underlying MPC protocol; a good value is 9223372036854775783 (BigInteger as String)

None

gid (optional, int)

ID of the group

maxElement (optional, string) - Maximum value the underlying MPC protocol shall accept (BigINteger as String)

None

mpcProtocol (optional, string)

MPC protocol to use.

numberOfItems (optional, int)

Number of items within a single data sets.

numberOfTimeSlots (optional, int)

Number of time slots (in other terms, how many data sets are expected). Negative values mean an infinite amount (pure streaming).

resultBufferSize (optional, number)

Size of the buffer for final results

Registration

gid (optional, number)

ID of the group.

registrationCode (optional, string)

The registration code.

Peer

gid (optional, number)

The group to which this peer belongs.

lastStatus (optional, stopped = 3)

None

peerName (optional, string)

A descriptive name for the peer (informational only).

peerType (optional, privacy peer = 2)

None

publicKey (optional, string)

The peer's public key.

registrationCode (optional, string)

The registration code used to register this peer.

url (optional, string)

The URL at which to contact the peer.

verified (optional, boolean)

Whether this peer has been marked as verified or not.

PeerConfigurationInfoCollection

peers (optional, list) - List of PeerConfiguration (peers)

None

PeerConfigurationInfo

finalResultsURL (optional, string)

URL to send final results to.

groupMgmtURL (optional, string)

URL of the group management service.

name (optional, string)

Name of the peer

peerType (optional, 2 = privacy peer)

None

privateKey (optional, string) - private key (base64 encoded)

None

publicKey (optional, string) - public key (base64 encoded)

None

registrationCode (optional, string)

Registration code

API Specification

Content-Type: text/plain

4.4

Content-Type: application/json

{"version":"4.4"}

Content-Type: application/json

{"global_parameters":{}}

Content-Type: application/json

{"global_parameters":{"expensesForIT":15000}}

Content-Type: application/json

{}

Content-Type: application/json

{"operational_cost_parameters":{}}

Content-Type: application/json

{"operational_cost_parameters":{"computationPowerCost":12,"skillRateMaintenance":1,"restartDuration":0.2,"usedStorage":1,"storageCost":5,"skillRateTests":0.7,"deploymentDuration":0.5,"businessApplicationsTestsDuration":4,"maintenanceDuration":10,"remediationCost":10,"remediationUninstallDuration":0.5,"usedPower":1,"serviceUnavailabilityDeploymentDuration":0,"skillRateDeployment":2,"workCost":20,"restartCost":0}}

Content-Type: application/json

{}

Content-Type: application/json

{"operational_cost_parameters":{}}

Content-Type: application/json

{"operational_cost_parameters":{"computationPowerCost":12,"skillRateMaintenance":1,"restartDuration":0.5,"usedStorage":0,"storageCost":10,"skillRateTests":1,"deploymentDuration":0.5,"businessApplicationsTestsDuration":6,"maintenanceDuration":0,"remediationCost":0,"remediationUninstallDuration":0.1,"usedPower":0.1,"serviceUnavailabilityDeploymentDuration":0,"skillRateDeployment":1.2,"workCost":20,"restartCost":10}}

Content-Type: application/json

{}

Content-Type: application/json

{"operational_cost_parameters":{}}

Content-Type: application/json

{"operational_cost_parameters":{"computationPowerCost":5,"skillRateMaintenance":1,"restartDuration":0.5,"usedStorage":0,"storageCost":3,"skillRateTests":0.7,"deploymentDuration":3,"businessApplicationsTestsDuration":4,"maintenanceDuration":0.5,"remediationCost":5,"remediationUninstallDuration":1,"usedPower":0,"serviceUnavailabilityDeploymentDuration":0.5,"skillRateDeployment":1.5,"workCost":20,"restartCost":10}}

Content-Type: application/json

{}

Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>
<idmef:IDMEF-Message xmlns:idmef="http://iana.org/idmef" version="1.0">
  <idmef:Alert messageid="abc123456789">
    <idmef:Analyzer analyzerid="bc-sensor01">
      <idmef:Node category="dns">
        <idmef:name>sensor.example.com</idmef:name>
      </idmef:Node>
    </idmef:Analyzer>
    <idmef:CreateTime ntpstamp="0xbc71f4f5.0xef449129">2000-03-09T10:01:25.93464Z</idmef:CreateTime>
    <idmef:Source ident="a1a2" spoofed="yes">
      <idmef:Node ident="a1a2-1">
        <idmef:Address ident="a1a2-2" category="ipv4-addr">
          <idmef:address>192.0.2.200</idmef:address>
        </idmef:Address>
      </idmef:Node>
    </idmef:Source>
    <idmef:Target ident="b3b4">
      <idmef:Node>
        <idmef:Address ident="b3b4-1" category="ipv4-addr">
          <idmef:address>192.0.2.50</idmef:address>
        </idmef:Address>
      </idmef:Node>
    </idmef:Target>
    <idmef:Target ident="c5c6">
      <idmef:Node ident="c5c6-1" category="nisplus">
        <idmef:name>lollipop</idmef:name>
      </idmef:Node>
    </idmef:Target>
    <idmef:Target ident="d7d8">
      <idmef:Node ident="d7d8-1">
        <idmef:location>Cabinet B10</idmef:location>
        <idmef:name>Cisco.router.b10</idmef:name>
      </idmef:Node>
    </idmef:Target>
    <idmef:Classification text="Ping-of-death detected">
      <idmef:Reference origin="cve">
        <idmef:name>CVE-1999-128</idmef:name>
        <idmef:url>http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-1999-128</idmef:url>
      </idmef:Reference>
    </idmef:Classification>
  </idmef:Alert>
</idmef:IDMEF-Message>

Content-Type: application/json

{"success":"IDMEF alerts added successfully"}

Content-Type: application/json

{"status":"Loaded"}

Content-Type: application/xml

<topology>
<machine>
<name>linux-user-1</name>
<security_requirement>7</security_requirement>
<interfaces>
<interface>
<name>eth0</name>
<ipaddress>192.168.1.111</ipaddress>
<vlan>
<name>user-lan</name>
<label>user-lan</label>
</vlan>
</interface>
</interfaces>
<routes>
<route>
<destination>0.0.0.0</destination>
<mask>0.0.0.0</mask>
<gateway>192.168.1.111</gateway>
<interface>eth0</interface>
</route>
</routes>
</machine>
<machine>
<name>linux-user-2</name>
<security_requirement>30</security_requirement>
<interfaces>
<interface>
<name>eth0</name>
<ipaddress>192.168.1.112</ipaddress>
<vlan>
<name>user-lan</name>
<label>user-lan</label>
</vlan>
</interface>
</interfaces>
<services>
<service>
<name>mdns</name>
<ipaddress>192.168.1.112</ipaddress>
<protocol>udp</protocol>
<port>5353</port>
<vulnerabilities>
<vulnerability>
<type>remoteExploit</type>
<cve>CVE-2007-2446</cve>
<goal>privEscalation</goal>
<cvss>10.0</cvss>
</vulnerability>
</vulnerabilities>
</service>
</services>
<routes>
<route>
<destination>0.0.0.0</destination>
<mask>0.0.0.0</mask>
<gateway>192.168.1.111</gateway>
<interface>eth0</interface>
</route>
</routes>
</machine>
</topology>

Content-Type: application/json

{"status":"Loaded"}

Content-Type: application/xml
Content-Length: 2174

<topology>
  <machine>
    <name>linux-user-1</name>
    <cpe>cpe:/</cpe>
    <interfaces>
      <interface>
        <name>eth0</name>
        <vlan>
          <name>user-lan</name>
          <label>user-lan</label>
        </vlan>
        <ipaddress>192.168.1.111</ipaddress>
        <directly-connected>
          <ipaddress>192.168.1.112</ipaddress>
        </directly-connected>
      </interface>
    </interfaces>
    <services />
    <routes>
      <route>
        <destination>0.0.0.0</destination>
        <mask>0.0.0.0</mask>
        <gateway>192.168.1.111</gateway>
        <interface>eth0</interface>
      </route>
    </routes>
    <input-firewall>
      <default-policy>ACCEPT</default-policy>
    </input-firewall>
    <output-firewall>
      <default-policy>ACCEPT</default-policy>
    </output-firewall>
  </machine>
  <machine>
    <name>linux-user-2</name>
    <cpe>cpe:/</cpe>
    <interfaces>
      <interface>
        <name>eth0</name>
        <vlan>
          <name>user-lan</name>
          <label>user-lan</label>
        </vlan>
        <ipaddress>192.168.1.112</ipaddress>
        <directly-connected>
          <ipaddress>192.168.1.111</ipaddress>
        </directly-connected>
      </interface>
    </interfaces>
    <services>
      <service>
        <name>mdns</name>
        <ipaddress>192.168.1.112</ipaddress>
        <protocol>TCP</protocol>
        <port>5353</port>
        <CPE>cpe:/</CPE>
        <vulnerabilities>
          <vulnerability>
            <type>remoteExploit</type>
            <goal>privEscalation</goal>
            <cve>CVE-2007-2446</cve>
          </vulnerability>
        </vulnerabilities>
      </service>
    </services>
    <routes>
      <route>
        <destination>0.0.0.0</destination>
        <mask>0.0.0.0</mask>
        <gateway>192.168.1.111</gateway>
        <interface>eth0</interface>
      </route>
    </routes>
    <input-firewall>
      <default-policy>ACCEPT</default-policy>
    </input-firewall>
    <output-firewall>
      <default-policy>ACCEPT</default-policy>
    </output-firewall>
  </machine>
</topology>

Content-Type: application/json

{"hosts":[]}

Content-Type: application/json

{"hosts":[{"security_requirements":[{"metric":"High","name":"sec-req-xml"}],"name":"linux-user-1"},{"security_requirements":[{"metric":"High","name":"sec-req-xml"}],"name":"linux-user-2"}]}

Content-Type: application/json

{}

Content-Type: application/json

{"attack_graph":{"arcs":{},"vertices":{}}}

Content-Type: application/json

{"score":""}

Content-Type: application/json

{"arcs":{}, "vertices":{}}

Content-Type: application/json

{"attack_paths":{}}

Content-Type: application/json

{"number":2}

Content-Type: application/json

{"attack_path":{}}

Content-Type: application/json

{"arcs":{}, "vertices":{}}

Content-Type: application/json

{"remediations":{}}

Content-Type: application/json

{"attack_graph":{"arcs":{},"vertices":{}}

Content-Type: application/json

{"success":"The remediation has been validated."}

Content-Type: application/json

{"alerts":[]}

Content-Type: application/json

{"finalResultsURL":"http://localhost:12001/p2ds-receiver/demo/receive","peerType":1,"name":"peerhans", "privateKey":"MFECAQAwEAYHKoZIzj0CAQYFK4EEACQEOjA4AgEBBDNyjBeP85atxkIfiYqW+0kUB2H3guXcQWXT/tXVktbn3MyUdRmNIL99G3rK1XoGSRAM6js=", "publicKey":"MH4wEAYHKoZIzj0CAQYFK4EEACQDagAEAJig6xXX4SuME5lRB2ADn7T7CgyH7LXbxy/oS5XhIElBPwz/40cwDAc/VgGbDKa+HGBc/AGzwSlScoCDHc7WA1tSkRUkaW/lL9NbA6gIzJLMw+FV3RPor0vpJIofVcAaV6WI1r99v8Y=", "registrationCode":"TEST", "groupMgmtURL":"http://localhost:12001/p2ds-group-management/group-mgmt"}

Content-Type: application/json

{"finalResultsURL":"http://localhost:12001/p2ds-receiver/demo/receive","peerType":1,"name":"peerhans", "privateKey":"MFECAQAwEAYHKoZIzj0CAQYFK4EEACQEOjA4AgEBBDNyjBeP85atxkIfiYqW+0kUB2H3guXcQWXT/tXVktbn3MyUdRmNIL99G3rK1XoGSRAM6js=", "publicKey":"MH4wEAYHKoZIzj0CAQYFK4EEACQDagAEAJig6xXX4SuME5lRB2ADn7T7CgyH7LXbxy/oS5XhIElBPwz/40cwDAc/VgGbDKa+HGBc/AGzwSlScoCDHc7WA1tSkRUkaW/lL9NbA6gIzJLMw+FV3RPor0vpJIofVcAaV6WI1r99v8Y=", "registrationCode":"TEST", "groupMgmtURL":"http://localhost:12001/p2ds-group-management/group-mgmt"}

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: application/json

{"peers":[{"name":"peerhans", "privateKey":"MFECAQAwEAYHKoZIzj0CAQYFK4EEACQEOjA4AgEBBDNyjBeP85atxkIfiYqW+0kUB2H3guXcQWXT/tXVktbn3MyUdRmNIL99G3rK1XoGSRAM6js=", "publicKey":"MH4wEAYHKoZIzj0CAQYFK4EEACQDagAEAJig6xXX4SuME5lRB2ADn7T7CgyH7LXbxy/oS5XhIElBPwz/40cwDAc/VgGbDKa+HGBc/AGzwSlScoCDHc7WA1tSkRUkaW/lL9NbA6gIzJLMw+FV3RPor0vpJIofVcAaV6WI1r99v8Y=", "registrationCode":"TEST", "groupMgmtURL":"http://localhost:12001/p2ds-group-management/group-mgmt"}]}

Content-Type: text/plain

Content-Type: application/json

{"peerName":"peerhans","data":"3;4"}

Content-Type: text/plain

Content-Type: text/plain

Content-Type: application/json

{"peerName":"peerhans","data":["3;4","1;1"]}

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

The data of the message as JSON.

Content-Type: text/plain

Content-Type: text/plain

Content-Type: application/json

{"gid":1,"lastStatus":0,"peerName":"peerhans","peerType":1,"publicKey":"MH4wEAYHKoZIzj0CAQYFK4EEACQDagAEAJig6xXX4SuME5lRB2ADn7T7CgyH7LXbxy/oS5XhIElBPwz/40cwDAc/VgGbDKa+HGBc/AGzwSlScoCDHc7WA1tSkRUkaW/lL9NbA6gIzJLMw+FV3RPor0vpJIofVcAaV6WI1r99v8Y=","url":"https://localhost:12001/p2ds-input-peer/peer"}

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: application/json

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

You need to upload the key as text/plain. The key needs to be transmitted as base64-encoded.

Content-Type: application/json

{"gid":1,"lastStatus":0,"peerName":"hanspeer","peerType":1,"publicKey":"MH4wEAYHKoZIzj0CAQYFK4EEACQDagAEAJig6xXX4SuME5lRB2ADn7T7CgyH7LXbxy/oS5XhIElBPwz/40cwDAc/VgGbDKa+HGBc/AGzwSlScoCDHc7WA1tSkRUkaW/lL9NbA6gIzJLMw+FV3RPor0vpJIofVcAaV6WI1r99v8Y=","url":"https://localhost:12001/p2ds-input-peer/peer"}

Content-Type: text/plain

Content-Type: text/plain

Content-Type: application/json

{"field":"1013","gid":"1","maxElement":"1000","mpcProtocol":"additive","numberOfItems":"2","numberOfTimeSlots":"2"}

Content-Type: text/plain

Content-Type: text/plain

Content-Type: application/json

{"peers":[{"gid":1,"lastStatus":0,"peerName":"hanspeer","peerType":1,"publicKey":"MH4wEAYHKoZIzj0CAQYFK4EEACQDagAEAJig6xXX4SuME5lRB2ADn7T7CgyH7LXbxy/oS5XhIElBPwz/40cwDAc/VgGbDKa+HGBc/AGzwSlScoCDHc7WA1tSkRUkaW/lL9NbA6gIzJLMw+FV3RPor0vpJIofVcAaV6WI1r99v8Y=","url":"https://localhost:12001/p2ds-input-peer/peer"},{"gid":1,"lastStatus":0,"peerName":"peerhans","peerType":1,"publicKey":"MH4wEAYHKoZIzj0CAQYFK4EEACQDagAEAJig6xXX4SuME5lRB2ADn7T7CgyH7LXbxy/oS5XhIElBPwz/40cwDAc/VgGbDKa+HGBc/AGzwSlScoCDHc7WA1tSkRUkaW/lL9NbA6gIzJLMw+FV3RPor0vpJIofVcAaV6WI1r99v8Y=","url":"https://localhost:12001/p2ds-input-peer/peer"},{"gid":1,"lastStatus":0,"peerName":"ppeer","peerType":2,"publicKey":"MH4wEAYHKoZIzj0CAQYFK4EEACQDagAEAJig6xXX4SuME5lRB2ADn7T7CgyH7LXbxy/oS5XhIElBPwz/40cwDAc/VgGbDKa+HGBc/AGzwSlScoCDHc7WA1tSkRUkaW/lL9NbA6gIzJLMw+FV3RPor0vpJIofVcAaV6WI1r99v8Y=","url":"https://localhost:12001/p2ds-privacy-peer/peer"},{"gid":1,"lastStatus":0,"peerName":"ppeer2","peerType":2,"publicKey":"MH4wEAYHKoZIzj0CAQYFK4EEACQDagAEAJig6xXX4SuME5lRB2ADn7T7CgyH7LXbxy/oS5XhIElBPwz/40cwDAc/VgGbDKa+HGBc/AGzwSlScoCDHc7WA1tSkRUkaW/lL9NbA6gIzJLMw+FV3RPor0vpJIofVcAaV6WI1r99v8Y=","url":"https://localhost:12001/p2ds-privacy-peer/peer"},{"gid":1,"lastStatus":0,"peerName":"ppeer3","peerType":2,"publicKey":"MH4wEAYHKoZIzj0CAQYFK4EEACQDagAEAJig6xXX4SuME5lRB2ADn7T7CgyH7LXbxy/oS5XhIElBPwz/40cwDAc/VgGbDKa+HGBc/AGzwSlScoCDHc7WA1tSkRUkaW/lL9NbA6gIzJLMw+FV3RPor0vpJIofVcAaV6WI1r99v8Y=","url":"https://localhost:12001/p2ds-privacy-peer/peer"}]}

Content-Type: text/plain

Content-Type: text/plain

Content-Type: application/json

{"gid":"1","name":"huhu"}

Content-Type: text/plain

Content-Type: application/json

{"name":"huhu"}

Content-Type: application/json

Content-Type: text/plain

Content-Type: application/json

{"gid":1,"lastStatus":0,"peerName":"peerhans","peerType":1,"publicKey":"MH4wEAYHKoZIzj0CAQYFK4EEACQDagAEAJig6xXX4SuME5lRB2ADn7T7CgyH7LXbxy/oS5XhIElBPwz/40cwDAc/VgGbDKa+HGBc/AGzwSlScoCDHc7WA1tSkRUkaW/lL9NbA6gIzJLMw+FV3RPor0vpJIofVcAaV6WI1r99v8Y=","url":"https://localhost:12001/p2ds-input-peer/peer"}

Content-Type: text/plain

Content-Type: application/json

{"gid":"1","registrationCode":"TEST"}

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: application/json

{"field":"1013","gid":"1","maxElement":"1000","mpcProtocol":"additive","numberOfItems":"2","numberOfTimeSlots":"2"}

Content-Type: application/json

{"field":"1013","gid":"1","maxElement":"1000","mpcProtocol":"additive","numberOfItems":"2","numberOfTimeSlots":"2"}

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: application/json

{"gid":"1","lastStatus":"1","peerName":"hanspeer","peerType":"1","publicKey":"MH4wEAYHKoZIzj0CAQYFK4EEACQDagAEAJig6xXX4SuME5lRB2ADn7T7CgyH7LXbxy/oS5XhIElBPwz/40cwDAc/VgGbDKa+HGBc/AGzwSlScoCDHc7WA1tSkRUkaW/lL9NbA6gIzJLMw+FV3RPor0vpJIofVcAaV6WI1r99v8Y=","registrationCode":"TEST","url":"https://localhost:12001/p2ds-input-peer/peer"}

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

Content-Type: text/plain

References

• FIWARE Open Specification License
• THALES
• ZHAW
• SEPIA
• https://www.ietf.org/rfc/rfc4765.txt
• https://www.ietf.org/rfc/rfc4765.txt
• https://github.com/fiware-cybercaptor/cybercaptor-data-extraction/blob/master/doc/topology-file-specifications.md