►
From YouTube: Demo: DIDIoT – A Decentralized Identity Framework for Internet of Things - Antonio Mateus, CPQD
Description
Demo: DIDIoT – A Decentralized Identity Framework for Internet of Things - Antonio Mateus, CPQD
The IoT has become a reality in our daily lives. Its applications range from simple temperature sensors to the communication of cars on a highway. Indeed, the devices now are in charge of collect and store sensible data from their owners, which makes them a target for hackers. However, securing the data in IoT environments is challenging due factors such as heterogeneity and device limitation. With this in mind, we from CPQD developed the DIDIoT, which consists in a decentralized identity framework for Internet of things. The DIDIoT applies the paradigm of decentralized identity and verifiable credentials to provide an additional security/privacy layer for the devices communication. The DIDIoT was implemented using the Hyperledger Aries framework. Our testbed tests shows that we can successfully enhance devices security by using the didcomm over the MQTT protocol to secure messages.
Sessions Details & Slides (if available): https://sched.co/15wCQ
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Discord: https://discord.gg/rVCn4j7UFd
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #Blockchain
License
Creative Commons Attribution license (reuse allowed)
A
Well,
hello,
everyone.
My
name
is
Fernando
Marino
I'm
from
the
Pico
d
I
and
I'm
here
to
talk
about
the
other,
centralized
identity
framework
for
in
terms
of
things.
Actually
it's
a
lab.
It
was
a
research
that
to
developed
on
CPD
cpqd
is:
it
is
a
research
center
in
Brazil,
okay,
we
are
where
we
are
searching,
blockchain
applications
and
so
the
application
of
self-server
identity
for
people
and
things
as
well.
A
Well,
a
little
bit
about
the
internet
of
things
that
you
know.
International
things
is
a
network
of
things.
A
network
that
connects
things
and
those
things
should
be
identifiable
advantage
of
things
is
what
difference
each
of
iot
devices
within
the
aux
systems.
It
is
about
how
to
identify
a
specific
device
in
ecosystems.
A
Okay,
so
here
is
an
example
of
iot
architecture
using
software
decentralized
identity.
This
was
a
common
concept
of
architecture.
You
know
you
have
here
the
applications,
the
business
applications
layer.
Then
we
have
the
cloud
servers
and
the
wireless
network
divided
the
sensor
Network
okay,
here
in
the
in
the
middle
of
that
we
have
the
iot
midwares,
where
those
iot
is
usually
connect
themselves
and
send
their
that
data
for
those
middlers.
A
Okay,
we
have
a
few
challenges
you
know
in
in
the
iot
field,
devices
devices-
usually
they
are
limited
in
terms
of
computer
power
devices-
can
be
compromised
and
enforce
to
propagate
invalid
informations.
So
we
are
not
sure
about
what
we
are
receiving
from
those
devices
and
Inter
interoperability
among
different
networks
and
a
guarantee
of
authenticity
and
integration
and
the
Integrity
of
data.
A
A
A
We
have
one
sensor
connecting
one
occupy
using
through
the
the
raspberry
and
we
have
a
analogy
using
an
occupy
directly.
Okay,
the
idea
here
how
it's
working.
We
have
to
change
the
Occupy
to
accept
the
mxdt
protocol.
Everybody
here
knows
the
mctt
protocol
iot
okay,
so
that
was
the
the
new
implementation
here.
It
was
to
adapt
the
iris
Cloud
HD
python,
to
transmit
data
using
Amica
t
so
how
it
is
working.
Well,
the
sensors
collect
data.
A
We
we
wrap
this
data
using
gdcon
protocol
using
connections
and
then
it
is
stands
about
using
the
MKT
protocol
for
the
agent
when
it's
come
to.
Dojo
Dojo
can
check
the
Jade
informations
and
the
signature
of
those
datas
that
was
sent
use
the
ddcom
protocol
okay.
So
you
have
a
kind
of
a
trust
layer
here,
granting
that
to
guarantee
to
the
meter
that
this
data
that
they
are
processing
now
came
from
the
specifically
sensor,
the
specific
iot.
A
Okay,
you
can
use
the
engine
as
well
to
exchange
credentials.
One
idea
that
I
have
here
was
to
share
a
particular
iot
I
mean
a
lot
of
mirrors
here,
using
the
same
iot
to
collect
data.
Both
the
iot
must
know
if
this
middle
is
allowed
or
not
to
collect
their
data.
So
the
owner
of
the
iot
device
issues
the
credentials
for
the
middle.
The
middle
show
these
credentials
for
the
device
the
device
check
it
verified
on
The,
Ledger
and
said.
A
Okay,
you
can
I
received
my
data
now
and
started
to
share
this
data,
which
is
another
iot.
That
is
particularly
interesting
in
the
field
of
5G
right
because,
at
least
in
the
development
in
development
countries
like
Brazil,
the
telk
was
the
most
to
share
their
devices
5G
or
it
should
not
work
properly.
A
The
security
layer
is
in,
we
are
using
the
common
security
approaches
to
guarantee
the
security
information
and
how
I'll
explain
a
little
bit
about
more
about
our
architecture.
Now
so,
as
I
told
you,
we
use
digital
platform,
Aries
agent
and
iot
device
the
roles
of
each
one.
Well,
the
dojo
is
our
iot
meter.
As
I
said,
it
established
the
connections
and
issuing
credentials
through
our
our
address
agent
and
finally,
the
informations
coming
from
the
device
and
is
accessible
in
the
web
platform.
A
Okay
authorizations
is,
are
the
centralized
radiations
here,
I
think
we
don't
have
many
doubts
about
that,
and
the
iot
device
is
properly
the
one
that
got
information
and
data
and
transfer
those
data
for
the
middle,
using
ddcom
or
proof
of
concept
goes.
What
was
our
goals?
First,
one
evaluate
the
framework
developed
and
in
a
test
environment,
it
was
built
a
lab,
detect
the
flaws
and
possible
improvements
in
the
concept
and
even
in
the
applications
and
the
final
Feature
work
for
This
research
present
and
present
the
conclusions.
A
A
The
dojo
agents
accept
this
connection
response
and
offer
accreditations
for
this
device.
Since
it
is
offered
the
device
accepts
it
or
not.
Usually
it's
accept
our
our
credentials
and
send
a
message.
You
use
the
sentimentions.
They
said
the
message
protocol.
Everybody
here
knows
the
send
message:
send
message:
Api
in
Aries
occupy
where
you
can
send
the
unstring
for
another
agent,
a
free
string.
We
use
it
to
transfer
data,
so
it
was
a
real
lab.
A
Okay
in
production,
we
have
to
develop
an
appropriate
channel
to
send
those
data,
but
here
only
to
try
you
use
the
send
message.
Api
rest
recent
message,
the
agent
to
handle
the
message
and
why
we,
why
does
your
agent
hand
the
message
because
we
developed
a
webi
hooker
and
we
are
checking
the
strings,
detecting
the
strings?
The
kind
of
those
messages
I
mean
it's
a
setup
message:
it's
a
data
transfer
message,
so
we
developed
a
protocol
to
detect
with
kind
of
a
message
we
are
receiving
from
our
relative
device.
A
Platform,
it's
open,
so
everyone
here
can
try
to
show.
We
use
a
local
in
the
network
using
the
phone
network
to
test
the
solution.
The
RS
Cloud
HD
python
that
we
use
it
is
the
version
1.0
17.0
we
use
a
hasberry
farm
model.
B
has
bear
Pi
OS
to
desktop
operation
systems
Arduino
and
a
sensor
to
collect
the
weather
informations.
A
Okay,
that
this
is
our
test
bad
here,
so
we
have
our
hazbearers
and
the
sensors
connected
with
the
hasberry.
This
has
Barry
has
a
an
AKA
Pi
agent
embedded
on
it.
The
difference
is
here
in
the
settings
of
occupy.
We
will
have
to
set
the
MX
the
m
key
mqtt
broker
configurations.
Okay,
so
you
have
a
broker
on
MKT
and
we
changed
the
Occupy
to
receive
these
informations
into
use
mqtt
as
its
main
protocol.
A
A
A
A
A
A
Okay,
we
created
the
invitation
here,
as
you
can
see
in
the
terminal
we
created
the
invitation.
The
invitation
was
created
by
the
iot
agent
and
it
was
sent
to
the
Dojo
agency.
So
it's
interesting
because
the
iot
must
know
the
end
point
and
the
address
the
president's
address
of
iot
meter
here
now
the
connection
is
okay,
it's
it
was
established
and
there
she
got
its
credential
and
in
the
dojo
each
device
works
like
an
agent.
So
you
can
see
here.
A
A
Are
conclusions
first,
based
on
the
this
prototype
that
we
developed
it's
possible
to
state
idd?
Can
the
centralized
identity
can
be
significant
to
to
in
iot
security?
Ddcon
has
an
increasing
key
layer
that
provides
messaging
Integrity
to
guarantee
that
the
the
content
that
was
sent
by
the
device
was
not
changed
by
itself.
A
The
creation
of
virtual
devices
or
digital
twins
associated
with
the
digital
identities
and
mqtt
transport
plug-in
for
interoperability
in
iotd
Networks.
Second,
finally,
we
important
unstable
test
scenarios
with
the
possibility
of
extensions
for
another
applications.
Fruity
works.
That
is
our
vision
right,
the
the
the
image
that
they
I've
shown.
You
show
you
how
it
was
in
terms
of
a
POC
looking
for
a
feature,
work,
there's
a
lot
of
things
to
do.
As
you
can
see,
we
have.
A
First
of
all,
we
have
another
protocols
that
must
be
integrated
with
the
Aries,
not
on
mqtt,
but
a
lot
of
one
and
and
others
we
have
to
the
perceptional
layer
because
we
don't
have
in
this
POC
the
perception
layer
I
mean
we
are
using
the
connection
layer,
The,
Hub
layer
using
has
barrier,
but
in
terms
of
security
we
have
to
connect
in
the
perceptional
layer,
I
mean
even
put
a
DOD
into
the
sensors.
That's
connecting
the
hobby.
A
Interoperability,
interoperability,
in
among
things
and
among
platforms
as
well
connect
with
another
platform.
Another
meters.
We
are
only
working
nowadays
with
Dojo
Miller,
but
it's
necessary
to
integrate.
For
example,
Bosch
a
bar,
the
Bosch
has
its
own
iot
meter
and
it
must
be
integrated
here
to
use
this
protocol
as
well
police
management
term,
we're
talking
about
governance,
for
example,
to
create
a
trust
layer.
Here
we
are
not
only
talk
about
technology
where
I
talk
about
how
we
can
create
a
trust,
a
trustable
environmental
address
environment
for
companies
and
agents.
A
A
A
A
Yeah,
no,
we
didn't
run
in
the
Arduino
device.
We
just.
We
only
use
the
raspberry
and
Iris
Cloud
python
agent,
I
mean
I,
don't
think
it's
possible
to
run
the
acapai
in
Arduino,
because
it's
not
have
support
for
Docker
or
something
like
that
and
in
this
research.
Specifically,
we
are
more
interested
about
the
protocols,
okay,
how
to
interpret
a
bit
because
at
the
first
time
we
have
a
doubt,
it
is
possible
to
use,
because
mqtt
is
a
very
short
protocol
and
the
ddcombe
as
it
is.
Nowadays,
it's
not
exactly
a
teeny
protocol.
A
It's
a
heavy
protocol
I
mean
so
it
works
it.
It
works
with
the
the
mqt
protocol.
I
got
I
got
myself
surprised
when
I
I
see
that
it's
working
pretty
well
with
MX
with
the
mqtt
protocol,
even
to
do
proof
of
credentials
issuing
credentials
not
only
to
send
a
message
rapid
in
a
ddcom
protocol.
That
was
surprised
for
me,
and
so
we
are
looking
for
that.
But
it's
it's
clear
for
us.
A
A
Here
we
have
seed
label
agent
here
I
received
because
it's
it's
a
here
in
in
the
Genesis
you
rely,
it
has
the
address
of
our
own
network.
So
we
built
a
whole
network
in-house
for
this
lab
and
it's
connecting
the
everybody
everybody
here
is
connected
and
he's
just
a
register
ad
in
the
in
the
network.
I
I,
don't
know
if
the
the
right
thing
to
do
I
mean
the
device
they
done
most.
They
don't
want
to
be
registered
in
the
in
the
in
The
Ledger
right.
Only
the
issuer
actually
need
need.
A
A
Oh
my
God,
yes,
the
engine
Integrations,
it
is,
you
know
we
are
using
the
RPC
I
I.
Guess
it's
not
at
the
end.
Integration
is
not
happening
using
MKT
protocol.
That's
your
question.
It's
not!
No!
No!
The
integration!
It's
we
didn't
handle
it.
So
the
integration
is
still
using
the
HTTP
protocol,
as
you
can
see,
you're
not
using
them
to
integrate
the
the
to
the
engine,
but
that's
a
great
idea.