Information Technology Reference
In-Depth Information
Table 2. Generic Grid Use Cases defined in the repository
Grid UC Name
User Register
Goals/Description
Register a user in the Grid before the user can send jobs or access to the Grid.
Scenario example
A new user fills in a form with information (username, role, domain, resource, credential type, etc.) and
the form is stored in the Grid.
Description
- A user gives information to register in the Grid system
- The Grid system processes this information and stores it in the Grid
- The user obtains the Grid system a username and password to log in.
Grid UC Name
Request of query
Goals/Description
Make a query to the Grid
Scenario example
A user wants to obtain information about a topic (pictures, news, videos, etc.) and s/he requests the Grid
with this query and waits for the results.
Description
- A query is received in the Grid
- The Grid processes the query and sent it to appropriate target
- The target executes the query and returns results
Grid UC Name
Data Retrieve
Goals/Description
Retrieve data requested
Scenario example
The Grid retrieves data of the resources indicated by the request
Description
- A request of retrieval of data has been authorized
- The request is processed and the task is sent to the resource where data is stored
- The resource returns requested data
Grid UC Name
Send results
Goals/Description
The results obtained are sent to the mobile device which initiated the request.
Scenario example
The results of a query are appropriately formatted to be shown on the screen of the mobile device.
Description
- The result of a query o request is obtained in the Grid when the task or subtasks have finished.
- The Grid studies the sender to know the resource display, memory, cpu, etc. and to send the results in
the right format
In this first iteration, we can identify several
possible types of threats to Information:
the stolen credentials of a legal user. Such
an attack could permit the disclosure or
modification of information, the execution
of unauthorized transactions, etc.
•
Unauthorized access
to Grid system. In
this scenario, the user wants to login the
system, so that we must ensure authorized
access.
•
Unauthorized disclosure
and
alteration of
information
. The user can send informa-
tion to the system or receive from the sys-
tem, so that we must protect the informa-
tion both transmitted and stored. Also we
must protect the personal information that
is transported through credentials.
•
Masquerade
. An attacker masquerades as a
certain user, access the Grid and sends re-
quests and obtains data from the Grid with
Step 2.4: Identify the Security
Use Cases and Misuse Cases
Once we have defined the most significant threats
and major assets to be protected in this first itera-
tion, we start with the identification, definition and
incorporation of security use cases and misuse
cases for the application.
In the repository, the main security use cases
for Mobile Grid environments, and misuse cases
that capture the behaviour of the main threats
identified in these environments are defined. We
Search WWH ::
Custom Search