|
OPC Security
Specification
Mission
Statement
|
To
address security issues as they relate to the OPC interfaces
including data access and historical. If possible, strong
user involvement in defining the requirements is particularly
desirable to this effort.
To
determine if an existing design (e.g. the enhanced N.T.
5 security model with user definable attributes) could
serve as a base for this effort (e.g. simply come up
with an OPC application note for applying NT 5 security
in a uniform way) or if a new set of OPC specific COM
Interfaces are a better solution.
If
new interfaces are required then this effort should
attempt to avoid changes to existing OPC Interfaces
and should instead attempt to define additional new
security related interfaces on existing OPC objects.
Keep
in mind the performace aspects of your decisions.
As
always, produce working sample code to prove the design
and provide an Automation wrapper if needed.
It
is believed that this effort should be fairly straight
forward and that a specification can be produced in
less than one year.
|
OPC
Security Specification Downloads
|
|