June 30, 2020 Project deliverable Open Access

Marco Manso

MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">API</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Third-parties equipment and services</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">SPHINX sandboxed environment</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Secure and trusted plug and play framework</subfield>
  </datafield>
  <controlfield tag="005">20200901114400.0</controlfield>
  <controlfield tag="001">3935788</controlfield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">1465231</subfield>
    <subfield code="z">md5:ced8d9df477fd68690cfc7c1a5fd450b</subfield>
    <subfield code="u">https://zenodo.org/record/3935788/files/SPHINX D3.6-Third Parties Enabling APIs v1-v1.00.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2020-06-30</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="p">user-sphinx</subfield>
    <subfield code="o">oai:zenodo.org:3935788</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">PDMFC</subfield>
    <subfield code="a">Marco Manso</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Third Parties enabling APIs v1</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-sphinx</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="c">826183</subfield>
    <subfield code="a">A Universal Cyber Security Toolkit for Health-Care Industry</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">https://creativecommons.org/licenses/by/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution 4.0 International</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;The SPHINX Application Programming Interface (API) for Third Parties (S-API) enables third-party solution providers to access and interact with the SPHINX Platform and its components. Subject to authentication, authorisation and using end-to-end encryption, S-API exposes advanced cybersecurity functionalities implemented by the SPHINX components, such as device/application certification, threat registry notification and anomaly detection. S-API therefore brings to SPHINX an easy integration with external components and the possibility for third-parties to extend existing SPHINX functionalities and incorporate additional functions. S-API also brings additional exploitation opportunities related with third-party&amp;rsquo;s services.&lt;/p&gt;

&lt;p&gt;This document presents the detailed design for the SPHINX S-API component, following the component&amp;rsquo;s introduction in the SPHINX architecture deliverable (D2.6 - SPHINX Architecture v2) [1]. It extends the technical specifications defined in [1] with the specific requirements for the component&amp;rsquo;s development, addressing its specificities, as well as interface specifications between S-API and the SPHINX components and third-parties. Importantly, it describes S-API interactions with third-parties and SPHINX services, which serve as a basis for the technical implementation of the S-API component in SPHINX.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.3935787</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.3935788</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">deliverable</subfield>
  </datafield>
</record>