One of the big challenges with cloud-based reputation checks is performance. Users do not typically want to wait a few seconds while the reputation of potential URLs is checked. Most of us have come to expect that websites are at the immediate tips of our fingers and that access and loading of the content should take place rapidly and immediately. This presents a tricky security problem. Since the reputation service exists in the cloud, the challenge can be summed up as, “How can a reputation be securely retrieved without slowing Web access down so much as to create a poor user experience?”
Answer the questions with an APA-formatted paper (Title page, body and references only). Your response should have a minimum of 500 words. Count the words only in the body of your response, not the references. A table of contents and abstract are not required.
A minimum of two references are required. One reference for the book is acceptable but multiple references are allowed. There should be multiple citations within the body of the paper. Note that an in-text citation includes author’s name, year of publication and the page number where the paraphrased material is located.
Your paper must be submitted to SafeAssign. Resulting score should not exceed 35%.
big challenges with cloud-based reputation checks
Introduction
Oops! Click Regenerate Content below to try generating this section again.
unstructured data
Unstructured data is hard to analyze. It’s often not available in a machine readable format, and it’s even harder to analyze by hand. This makes unstructured data difficult to use for automated processes like reputation checks and fraud detection.
blacklists are outdated
Blacklists are outdated. They’re not updated and they don’t have granularity to them. This means that if a site is listed on a blacklist, it will continue to show up in search results forever.
Blacklists are static and can’t be dynamic. If you want your company or brand to be found by potential customers, then the best way is through an automated system that allows for ongoing updates based on real-time research from online data sources like Google Analytics or Bing Ads.
Blacklists aren’t specific enough; they include generic terms like “phishing” or “malware,” which could mean anything from fake emails sent by scammers trying to trick people into clicking links inside them (phishing) all the way up through malicious software designed specifically for stealing personal information from users’ computers (malware).
most networks are firewalled
Most networks are firewalled. Firewalls are a problem for reputation checks because they can block traffic. You might expect that most people know how to configure their firewall, but this doesn’t always happen and it’s easy to make mistakes when configuring the firewall on your network.
Most firewalls have rules that allow only certain types of traffic through the system, so if you want to send a message with a link in it (like we did above), then your message will be blocked by the firewall until you remove all references to websites or URLs that may be blocked by default settings within your organization’s security policy (and possibly other organizations’ as well).
device use is so variable and rapidly changing
As device use is changing constantly, cloud-based reputation checks are not good at handling this variability.
In the case of IoT devices like sensors and smart home appliances, it’s not uncommon for them to be used in ways that are not always predictable. For example, some people might leave their door unlocked when they go out for the evening but lock it after returning home from work because they don’t want intruders entering their house through an unlocked door. This can lead to unexpected problems with these devices; if someone tries accessing your IoT camera’s feed while you’re away from home but doesn’t have permission (or isn’t authorized), there could be issues!
device traffic varies wildly day to night and locally
The device traffic varies wildly day to night and locally. This makes it difficult for a cloud-based reputation check system to be able to accurately determine whether or not someone’s account is being used fraudulently. For example, if you have a smartphone with you all the time, then your usage pattern will be similar every day—you might visit your bank while walking down the street or taking care of some other business during lunch hour at work. However, if you’re traveling abroad and happen across some local currency exchange shops while out sightseeing one afternoon (or even breaking into an ATM), this could mean that any activity on your account would show up as suspicious activity due to its location in relation both time zone differences between countries where U.S.-based financial institutions’ services may be available but not necessarily available everywhere within those countries themselves without additional effort being required from customers concerned about these issues themselves beforehand before traveling abroad instead of relying solely upon third party software solutions provided by providers such as PayPal which could potentially cause problems when trying
data retention
Data retention is another challenge with cloud-based reputation checks. The amount of data you have to store depends on the size of your company and how often you plan on using it. For example, if you’re only looking at a handful of reviews each day, then keeping that information for a few months won’t be much trouble. But if you want to keep track of every single review—and there are many different types of businesses who would benefit from this kind of service—then it can get complicated quickly.
How long do I need to keep my data? It might seem obvious that not all companies should have their entire records stored forever (and some are even prohibited from doing so), but how long should we expect our customers’ info to stay around? If someone buys something from us online today but doesn’t leave us positive feedback until tomorrow morning…do we still need access now when we’re still trying hard not just look at negative reviews but also positive ones too?
The answers come down mostly on industry standards: some companies may require storing certain types only temporarily while others will allow them indefinitely; some may require deleting older versions altogether while others think otherwise—so again there’s no right answer here! But whatever decision ends up being made must take into account both legal requirements as well as practical considerations like cost and storage capacity before making any decisions about what type(s) should be kept forever versus temporarily archived.”
a lot of challenges!
Data is a big issue. There’s no way around it, and the more data you have, the better your results will be. But that doesn’t mean you should just throw every piece of data into your cloud-based reputation checks—you need to filter it properly.
The first challenge with cloud-based reputation checks is unstructured data: most networks are firewalled and device usage is so variable and rapidly changing that any given day could see an unbelievable amount of traffic flow through them. Device use varies wildly day to night and locally; even if someone does use their laptop in one location for several hours at a time (and we’ll get into why not later), there are still many other factors at play like where exactly on their network they’re located; whether or not they’re connected via cellular or WiFi; whether or not they’re connected via VPN/proxy services; whether or not they’ve set up port forwarding rules on their router(s); etcetera etcetera ad infinitum (you get where this is going). All these factors contribute significantly towards determining how much information gets transmitted between two parties—and thus which companies can access valuable signals within such signals’ streams!
Conclusion
Section: data retention – This section is about how much data your company has and where it is stored.
Takeaway: Data retention is a big problem, but the solution can be complex if you are not careful.
Encrypted communication – The second part of the policy discussion was whether or not to encrypt our communications with other companies in our supply chain like miners, manufacturers, etc. There are many difficulties to this topic including encryption keys management and making sure that we only talk to trusted parties on their devices. But there may be a business case for encrypting these communications as some miners have already implemented encryption by default. So unless you consider your cloud vendor an untrusted party then it is likely to make sense for your company to implement this practice as well!
Takeaway: Encryption can help protect your company from legal trouble and bad PR but does not protect against physical theft or hacking by third parties (unless you have top-tier security). Encryption should be used carefully. Never share your encryption keys with any party outside of crypto-currency communities such as Bitcoin forums!