back to article ID and the triple-A challenge of mashup security

The loose coupling of data drawn from different systems is one of the enduring appeals of mashups. However, what if some of that data needs to be handled securely, or it is necessary to log in to some or all of the data feeds? What if the mashup as a whole represents some form of sensitive system - now security is an issue. …


This topic is closed for new posts.
  1. Larry Cumber

    Security !

    Mashing up data has its consequences. I believe that's why we have to see that,Deep data protection is taken into consideration when building robust database to hold this data.

    It would preferably be nice for security to be linked to certain policies that can be granted to rows. This would therefore limited applications being the gateway to insecurity.

    But notwithstanding for authenitcation and authorisation to take place and followed by a single-sign-on process. Id's would still be in use. Identifying,recognising and accepting has lots to play.....I believe it would be nice to have data stored in another medium--but what would that be is the question.

This topic is closed for new posts.