Skip to main content
Advertisement
Browse Subject Areas
?

Click through the PLOS taxonomy to find articles in your field.

For more information about PLOS Subject Areas, click here.

< Back to Article

Table 1.

Limitations and compatibility issues of existing integrity schemes in Clouds.

More »

Table 1 Expand

Fig 1.

Black box architecture of provenance based data integrity verification.

More »

Fig 1 Expand

Fig 2.

Collection of provenance data from different layers of abstraction in Clouds.

More »

Fig 2 Expand

Table 2.

Various attributed with their description and corresponding layer of Cloud environment.

More »

Table 2 Expand

Fig 3.

Various components of integrity service (integrity tracker phase).

More »

Fig 3 Expand

Fig 4.

Architecture of DataStore application with different layers of abstraction.

More »

Fig 4 Expand

Fig 5.

Visualization of integrity leaks to the end user.

More »

Fig 5 Expand

Table 3.

System details for evaluation.

More »

Table 3 Expand

Fig 6.

Results of the calculated time (minutes:seconds format) with and without the provenance for Eucalyptus Walrus.

More »

Fig 6 Expand

Fig 7.

Cost of provenance collection in terms of elapsed time (in seconds) for different number of objects.

More »

Fig 7 Expand

Fig 8.

Cost of provenance storage (disk space in Kilo bytes) for different number of objects.

More »

Fig 8 Expand

Table 4.

Comparison of existing integrity schemes in Cloud.

More »

Table 4 Expand

Table 5.

Comparative analysis of proposed scheme with existing data integrity schemes.

More »

Table 5 Expand