[Fiware-security] Open Call topic for T8.4

[Waller, Adrian]

Dear Francesco,
	Looking at your description for the required asset and the
spreadsheet you previousy sent, our Content Based Security asset already
proposed for Task 8.4 (and which has backlog entries) would appear to meet
the requirement. So, I don't think we need an Open Call on this.

Regards,

Adrian

Dr. Adrian Waller CISSP
Technical Consultant - Information Security
Thales UK
Thales Research and Technology (UK) Ltd., Worton Drive, Reading  RG2 0SB,
U.K.

[www.thalesgroup.com/uk]
Tel:   ++44 118 923 8304 Fax:  ++44 118 923 8399
e-mail:	Adrian.Waller at thalesgroup.com  




 

> -----Original Message-----
> From: fiware-security-bounces at lists.fi-ware.eu 
> [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf 
> Of DI CERBO, Francesco
> Sent: 12 December 2011 17:46
> To: BISSON Pascal <pascal.bisson at thalesgroup.com> 
> (pascal.bisson at thalesgroup.com)
> Cc: fiware-security at lists.fi-ware.eu
> Subject: [Fiware-security] Open Call topic for T8.4
> 
> Dear Pascal,
> 
> As previously announced, please find the description of the 
> open call topic for T8.4.
> 
> I noticed that in the minutes, you make a reference to a 
> google doc spreadsheet. Just to test if I got it right:
> 
> - we are supposed to mention the UC tickets that we analyzed 
> there, copying the MoSCoW priority assigned by the requestor 
> UC, AND expressing our final evaluation (using MoSCoW 
> classification) to explain if and with which priority a 
> ticket shall be accepted by us. Right?
> 
> Questions:
> 
> 1) each tab has a project name associated to it; in columns, 
> however, there are also the name of all other UC projects: 
> this is meant in case of joint requests by a number of UC 
> projects? Or if we detect a cross-cutting problem/request, we 
> can use those columns to make links among tickets?
> 2) how are we expressing if a ticket is covered just to a 
> certain extent by a GE? For instance, how do we express if a 
> ticket is covered at 50% by a GE?
> 
> Thanks a lot for the clarification!
> 
> Francesco 
> 
> _______
> 
> Title: Secure communication asset
> 
> Description: The asset must support authenticated and 
> encrypted communications between different actors, ensuring  
> confidentiality and security to end points. The asset must 
> work at application level as a proxy, and expose ReST and 
> SOAP interfaces. The asset must support the identification of 
> endpoints simply using cryptographic tools, i.e., a pair 
> public-private RSA keys, but not limited to it.  It must 
> provide an encryption/decryption API, and support at least 
> the following encryption protocols: DES, AES, RSA, TEA, SHA-0 
> and SHA-1.
> 
> UC requests covered by the asset:
> INSTANMOBILITY.Epic.Security.SecureTransaction  
> https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=362
> &group_id=7&atid=163
> 
> (even if some more explanations could be asked, to ensure 
> that they are really interested to application-level 
> security) OUTSMART.Epic.Security.EncryptedCommunications 
> https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=474
> &group_id=7&atid=163
> 
> ___
> 
> Francesco Di Cerbo, PhD
> SAP Labs France
> 805, avenue Maurice Donat
> Font de l'Orme
> BP 1216
> 06250 Mougins Cedex
> France
> Tel. +33 4 92 28 64 45
> e-mail: Francesco.Di.Cerbo at sap.com
> 
> 
> _______________________________________________
> Fiware-security mailing list
> Fiware-security at lists.fi-ware.eu
> http://lists.fi-ware.eu/listinfo/fiware-security
> 


Please consider the environment before printing a hard copy of this 
e-mail. 
 
The information contained in this e-mail is confidential. It is intended 
only for the stated addressee(s) and access to it by any other person is 
unauthorised. If you are not an addressee, you must not disclose, copy, 
circulate or in any other way use or rely on the information contained in 
this e-mail. Such unauthorised use may be unlawful. If you have received 
this e-mail in error, please inform us immediately on +44 (0)118 986 8601 
and delete it and all copies from your system. 
 
Thales Research and Technology (UK) Limited. A company registered in 
England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne 
Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 
774298 
 
Thales UK Limited. A company registered in England and Wales. Registered 
Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, 
Weybridge, Surrey KT15 2NX. Registered Number: 868273 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PPP_FIWARE_ASSETS_Description of the Optional Security Assets.docx
Type: application/octet-stream
Size: 19126 bytes
Desc: not available
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20111213/00bf8dcd/attachment.obj>