Security Requirements - Edited.edited

Running head: SECURITY REQUIREMENTS 1
Security requirements
Students Name:
Professors Name:
Course:
Date:
SECURITY REQUIREMENTS
2
Due to the gradual changes in the technology, there are several classifications of
requirements varying from top business requirements to the comprehensive technical
specifications that describe a complicated part of a computer hardware device or algorithm
(Anwar et al. 2017). With this in mind, we will discuss who utilizes the requirements, how to
implement security requirements, and why good requirements go bad.
Concerning the expertise of the recipient and architects, it may be satisfactory to pen
down a requirement that talks about an object in the manner of congestion to the app server
should only be authorized from the net cancellation network to the app server. Only permit
HTTP traffic. Reject all other congestion from the web cancellation net to the app server. Under
circumstances in which adjustments to the revealed systems have to undertake remarkable
construction and planning tasks within the network group, an essential requirement may be
needed. If the network task already has impressive expertise and investment, excellent existing
network tools and architectures, the elements can undertake those abilities. Similarly, if web
layers are completely the latest idea, more specification may be needed even to the specific tool
that will administrate the layering.
The aphorism for acquiring requirements to the correct specification level is sufficient to
provide an execution that will match the security objectives. For instance, a security architect is
not bothered with how limitations are applied but preferably that it will be difficult for an
intruder to use the eliminating network. DMZ, as a foothold to strike the app server, the security
architect is concerned about averting a loose of control of the bastion net to damage the whole
environment beginning with the app server. This implicates that congestion in the app server
should be confined to only the structures that should be conversing with it, with congestion
coming from cancellation to the app server, not the other way around.
3
Getting security requirements implemented is possible through agile software (de Vicente
Mohino et al. 2019). The objective of agile is an intense commitment build on faith and
individual reliability. Since agile software allows the design to come out of an innovative,
productive, and automatic process tries to issue edicts and anticipate flawless constancy to fly
instantly in the face of how profits of agile are to be produced. Agile is an immediate reaction to
control governance processes and command. Administration based on stern compliance is meant
to break down, or the agile will not succeed since they are entirely incompatible. Firstly, there
must be enough architecture as well as an armature, an architecture scaffolding upon which the
quick, productive procedure can build. The architecture scaffolding will be created in the usual
waterfall procedure prior to handing over to sprint teams. Not forgetting whether agile or not
something will change in the process of formation.prolonged creation sequence, increases the
possibility for something to transform, which causes issues that cause trouble in applying
security requirements in the system.
There are several ways in which proper requirements go wrong. For instance, when the
architecture plan has been altered during instigation, the elements cannot be applied as directed.
This is because some of the software cannot be restricted to a particular app meaning that it's a
lousy requirement with proper motives but did not consider real-world architecture and potentials
of the structure enhancing the application. Finally, there are situations where talented individuals
go too far. This is because they are paid to deliver in time; hence they opt to take shortcuts to
success, meaning that they limit as many requirements as possible. This means that they try to
manipulate the process to the ground that my add objects for delivery as security does. This may
also cause functional requirements to go wrong, but the availability of governance helps solve
these cases for the profitability of the organization and system.

4
References
Anwar, S., Mohamad Zain, J., Zolkipli, M. F., Inayat, Z., Khan, S., Anthony, B., & Chang, V.
(2017). From intrusion detection to an intrusion response system: fundamentals,
requirements, and future directions. Algorithms, 10(2), 39.
de Vicente Mohino, J., Bermejo Higuera, J., Bermejo Higuera, J. R., & Sicilia Montalvo, J. A.
(2019). The application of a new security software development life cycle (S-SDLC) with
agile methodologies. Electronics, 8(11), 1218.

Security Requirements - Edited.edited

Uploaded by

Copyright:

Available Formats

Security Requirements - Edited.edited

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Security Requirements - Edited.edited

Uploaded by

Copyright:

Available Formats

Running head: SECURITY REQUIREMENTS 1

requirements varying from top business requirements to the comprehensive technical

specifications that describe a complicated part of a computer hardware device or algorithm

implement security requirements, and why good requirements go bad.

circumstances in which adjustments to the revealed systems have to undertake remarkable

that will administrate the layering.

security requirements in the system.

these cases for the profitability of the organization and system.

(2017). From intrusion detection to an intrusion response system: fundamentals,

requirements, and future directions. Algorithms, 10(2), 39.

agile methodologies. Electronics, 8(11), 1218.

You might also like