Answer:
The basic comaprism of OSSTMN and PTES includes the following: OSSTMN is more theoretical, security assessment methodology, and Metrics based why PTES is technology oriented, penetration testing methodology
, extended analysis of all stages
Explanation:
Solution
Penetration testing has several methodologies which include :OSSTMM and PTES
The comparison between OSSTMM and PTES is stated as follows:
OSSTMM:
Security assessment methodology
More Theoretical
Metrics based
PTES
:
Technology oriented
Penetration testing methodology
Extended analysis of all stages
Now,
There are 7 stages which is used to define PTES for penetration testing.(Penetration Testing Execution Standard)
- Pre-engagement Interactions
Now,
The OSSTMM is used to obtain security metrics and performing penetration testing .The OSSTMM provides transparency to those who have inadequate security policies and configurations.
The OSSTMM includes the entire risk assessment process starting from requirement analysis to report creation.
Six areas are covered by OSSTMM which are:
-
Internet technology security
Answer:
Pseudocode is as follows:
// below is a function that takes two parameters:1. An array of items 2. An integer for weight W
// it returns an array of selected items which satisfy the given condition of sum <= max sum.
function findSubset( array items[], integer W)
{
initialize:
maxSum = 0;
ansArray = [];
// take each "item" from array to create all possible combinations of arrays by comparing with "W" and // "maxSum"
start the loop:
// include item in the ansArray[]
ansArray.push(item);
// remove the item from the items[]
items.pop(item);
ansArray.push(item1);
start the while loop(sum(ansArray[]) <= W):
// exclude the element already included and start including till
if (sum(ansArray[]) > maxSum)
// if true then include item in ansArray[]
ansArray.push(item);
// update the maxSum
maxSum = sum(ansArray[items]);
else
// move to next element
continue;
end the loop;
// again make the item[] same by pushing the popped element
items.push(item);
end the loop;
return the ansArray[]
}
Explanation:
You can find example to implement the algorithm.
Answer:
Explanation:
<u>Ways to Avoid Scope Creep</u>
Scope creep is what happens when changes are made to the scope of a project without any control. Changes happen to projects all the time without been notify ontime as a project manager. It is that very rare project that ends up delivering exactly what was asked for on the first day. However, without there being some control over the changes, a project manager has little chance of keeping on top of the work and managing the project effectively.
Generally, scope creep is when new requirements are added after the project has commence. These changes are not properly reviewed. The project team is expected to deliver them with the same resources and in the same time as the original scope.
On the other hand, as a project manager you could end up with a project with lots of approved, considered changes, that never ends because every time you think you have finished a new requirement arrives in your inbox and you have to make more changes.
The following are five ways to keep control of your project.
<em>1-Document the Requirements</em>
<em>2-Set up Change Control Processes</em>
<em>3-Create a Clear Project Schedule</em>
<em>4-Verify the Scope with the Stakeholders</em>
<em>5-Engage the Project Team</em>
