Place your order now for a similar assignment and have exceptional work written by our team of experts, At affordable rates

For This or a Similar Paper Click To Order Now

Do Not plagiarize or copy info/ source from any student paper. I need 100 original works because my school uses an advance plagiarize checker!!
THIS IS NOT A ESSAY! EACH CLASS IS DIFFERENT!
CIS 512: Advanced Computer Architecture
Please respond to the following in a post of at least 200 words:
Week 6 Discussion
Some organizations receive confidential e-mails and take specific steps to protect and label these e-mails.
Go to Basic Search: Strayer University Online Library to locate and integrate at least two quality, academic resources (in addition to your textbook) on the protection and labeling of confidential emails. You may also use government websites, such as Cybersecurity from the National Institute of Standards and Technology.
Please respond to the following in a post of at least 200 words:
· Describe the methods organizations use to protect and label confidential e-mails.
· Identify and describe any laws, such as the General Data Protection Regulation (GDPR), or legal requirements, such as eDiscovery, by which organizations may be required to abide.
· Provide full citations and references, formatted according to Strayer Writing Standards.
· For assistance and information, please refer to the Strayer Writing Standards link in the left-hand menu of your course. Check with your professor for any additional instructions.
In 60 to 75 words, please respond to at least one other post. Choose to respond to those who have few or no responses.
Note: You will find it helpful to use the information from this post and the feedback you receive on it in your assignment due this week.
Classmate recommendation below please rewrite a respond:
Describe the methods organizations use to protect and label confidential e-mails.
·
A Data Loss Prevention (DLP) can be used to determine when an e-mail should be encrypted. For instance, DLP can search all e-mails for
A particular text can be used in the subject line to determine if an e-mail should be encrypted. For example, it can be configured so that if the user puts “” in the subject of an e-mail, that e-mail will be encrypted.
A third option is to have an Outlook plugin that the user can use to select when they want to encrypt an e-mail.
Identify and describe any laws, such as the General Data Protection Regulation (GDPR), or legal requirements, such as eDiscovery, by which organizations may be required to abide.
There are no specific GDPR email requirements. This is because compliance with the General Data Protection Regulation applies to all methods used to collect, process, share or store EU citizens’ personal data, and not just email. The contents of the e-mails are what’s covered by GDPR.
William Stallings. 2019. Effective Cybersecurity: A Guide to Using Best Practices and Standards.
Spam Titan, GDPR Email Requirements, https://www.spamtitan.com/gdpr-email-requirements/#:~:text=Strictly%20speaking%2C%20specific%20GDPR%20email%20requirements%20do%20not,EU%20citizens%C2%B4%20personal%20data%2C%20and%20not%20just%20email
3. GDPR.EU, How does the GDPR affect email?, https://gdpr.eu/email-encryption/
CIS 515:
Strategic Planning for Database Systems
– Please respond to the following in a post of at least 200 words:
Week 6 Discussion
In order to ensure optimal database performance, the logical and physical design should consider the user requirements thoroughly. Suppose you have been hired to transform a conceptual model into a logical model for a sales database.
· Describe the specific steps that you must perform in order to appropriately construct the database model.
· Speculate the risks that might present themselves for each step mentioned, and how you would avoid or mitigate those risks.
· Be sure to respond to at least one of your classmates’ posts.
Classmate Suggestion below please rewrite a respond:
To move to a logical design from conceptual, we would need to perform refinement of the conceptual design to arrive at the logical design required. To go through the refinement process, we must look to identify and resolve any relationship complexities such as cardinality, redundancies, and recursive relationships. To better explain the refinement of cardinality, we will use the conceptual model to identify the cardinality as is. Once this is accomplished, we will want to resolve any many-to-many relationships that are present. Typically, these M:N relationships are decomposed and new entities are created to create more natural relationships between the new entities and their attributes. With these new intermediate entities, we can bridge the relationship using any cardinality other than M:N. Resolving any other complexities are similar in fashion as they require decomposing the M:N relationships to create intermediate entities.
Some risks that we may run into include integrity loss during the logical design. As we expand our use of entities to reduce the complexities, we must ensure our constraints are set to prevent loss of integrity. There are four constraints we can address to mitigate the risk of integrity loss which are Necessary Data, Entity and Referential Integrity, and finally Domain Constraints. Each of these provide valuable support for the logical design where all necessary information is clear and identifiable. By marking an attribute as Necessary Data we can ensure there is no null value for such attributes. Using Entity and Referential integrity we make an entity hold a primary key with a non-null value and all foreign keys are referencing a valid parent key. Finally, Domain Constraints help to provide correct data types for the data being held within a domain which would otherwise run into an error as the type of data expected did not match what was given. Without these integrity constraints, the logical design would quickly fall apart as necessary information could be missing along with improper relationships or references to data that does not exist.
Reference:
https://strayer.ucertify.com/?func=ebook&chapter_no=6 – Database Design Specialist v1.1

For This or a Similar Paper Click To Order Now