Category: Security

  • How To Fix iPhone 7 And 8 Home Button Not Clicking Or Ripped And Torn While Keeping Touch ID

    How To Fix iPhone 7 And 8 Home Button Not Clicking Or Ripped And Torn While Keeping Touch ID

    Symptoms

    Your home button will not click or work but your Touch ID / Fingerprint reader may still work perfectly fine. This is a major issue with the iPhone 7, iPhone 7 Plus, iPhone 8, iPhone 8 Plus and all the previous models.

    Reason

    Your screen probably cracked and you decided to get it fixed yourself or at a non-apple authorized center. In the process of moving the home button from the old screen to the new one the home button got ripped, sometimes it’s a tiny tear that can’t be seen except with a microscope. That tiny tear can cause your home button not to click.

    Is There a Temporary Fix?

    The only workaround for it is to enable assistive touch, this will give you an on-screen menu that you can use as a home button alternative, to use that feature follow the step listed below (note: if you’re stuck on the lock screen, swipe left and type settings):

    Settings > General > Accessibility > AssistiveTouch > AssistiveTouch (switch to on)

    Once you have it turned on, it’ll look like something like this:

    The only real solution is listed below, we accept mail-in-orders for iPhones if you’d like us to get it taken care of. 

    How to Permanently Fix

    In order to get the iPhone 7 or 8 or any of the older models that has a broken home button or a ripped home button fixed, you need to take the iPhone apart to get to the home button and then use special micro-soldering tools to rewire the components on the home button flex cable that were ripped so they’ll function again. Special and advanced tools are required to do this repair, these tools include a microscope, heat gun, and everything needed to reroute the traces on a flex cable. Only micro-soldering techs with logic board repair experience are capable of getting this repaired successfully, if you put too much heat on the home button or mistakenly move other components around as you’re soldering then you could easily cause permanent damage to your iPhone.
    We strongly urge you to look for a local repair shop near you and make sure they do micro soldering as we do not recommend anyone to attempt this repair without prior experience, if you can’t find any near you, we offer nationwide mail-in-repairs with free shipping both ways, to get your order started simply 

    Via: https://cellphoneninja.co.za/blog

  • Endpoint security and cloud architecture

    Endpoint security and cloud architecture

    Hackers love endpoints—those end-user devices that connect to your enterprise network. With a little ingenuity, bad actors (outside or inside your organization) can access sensitive data through employees’ laptops and smartphones, the office security cameras, printers, and a host of other entry points.

    Endpoint security protects your enterprise resources by safeguarding these end-user devices from breach or physical theft. But many organizations are asking how cloud computing fits into the equation. In this brief interview, Pluralsight instructor Terumi Laskowsky (TL) walks through the considerations and responds to frequently asked questions.

    How has endpoint security changed in the era of cloud?

    TL: A decade ago, organizations typically limited the type of end-user devices that could connect to the corporate network, which gave IT professionals significant control over device security.

    In contrast, cloud involves broad network access, and the possible devices that can access the cloud are growing exponentially and more geographically distributed.

    Gone are the days where equipment lived primarily on a corporate campus, accessed through highly secure VPN connections. Today’s devices often access the corporate network via the cloud, without this enhanced scrutiny in place.

    Many enterprises utilize a hybrid deployment model where the cloud is an extension of on-premises infrastructure. This requires security professionals to consider an ever-growing assortment of endpoint devices, which all represent potential attack vectors and require risk management strategies to protect corporate resources and data.

    How do you protect endpoints?

    TL: First, it’s important to recognize that a device can be an attacker or a victim. So, you have to plan for both scenarios. How do you protect a device from a cyber attack? And how do you protect your corporate resources against a compromised device?

    You can install an endpoint security solution in a device and control its behavior using an organizational security policy. For example, to protect data leakage from these devices, the security policy could prohibit using USB sticks. Here’s another example: You could enforce whole-disk encryption in case someone loses their end-user devices. This is easier to do if your organization owns and manages the devices.

    However, many employers allow personally owned devices to connect to the corporate infrastructure, especially from the cloud. This complicates the matter. If you allow your company to install an agent on your phone, who has control over your phone? How about your private data on the phone? Is your privacy protected? Organizations need to think through and resolve these questions.

    What should an endpoint protection strategy include?

    TL: Organizations need to catalog all devices that access corporate resources—from computers and smartphones to IoT devices such as fire alarms, thermostats, the sensors where employees swipe their badges to gain access to your building, and an ever-growing assortment of smart technology.

    Anything that connects to your corporate resources can be a point of entry for a cyberattacker. This means you need a process for constantly updating your inventory of endpoint devices and managing each via an endpoint security corporate policy.

    Your strategy also needs to identify who owns the responsibility for maintaining the security of each endpoint device. In some cases, the answer is IT. In other cases, you’ll need a formal shared responsibility agreement. For example, your facilities team maintains your thermostats. What aspects of security will they be responsible for? And what will IT handle?

    This can’t just be an exercise on paper—a document that sits on a shelf and collects dust. When there’s shared responsibility, both parties need to formally acknowledge they understand their role. And you need an oversight process that periodically audits security for each of the endpoint devices.

    When organizations don’t plan for shared responsibility, security can fall through the cracks.

    Actor Henry Winkler said, “Assumptions are the termites of relationships.” In my opinion, they also are the termites of cybersecurity. A good endpoint security policy clearly articulates who is responsible for the security of each device so there are no assumptions or oversights.

    T. Laskowsky

    How does the cloud deployment model affect endpoint security?

    TL: Here’s a rule of thumb to consider when planning your cloud strategy:
    Complexity increases overall security risk and complicates endpoint security planning.

    If 100% of your corporate resources live in a private cloud (single tenant = you), your endpoint security planning is easier than with a multi-tenant public cloud.

    When you have part of your corporate resources in one spot—say, an on-prem data center—and the rest with a public cloud provider (a hybrid cloud approach), you need security planning for both sets of resources. The complexity of connecting the two increases the risk of security vulnerabilities. Same with multicloud, where you’re utilizing two or more public cloud providers.

    Each of these models requires a different level of effort to manage security risk.

    What are endpoint security best practices when the cloud is involved?

    TL: Applying security controls to the endpoint is just one step. Organizations must also apply security controls to the critical resources, such as network, database, email systems, to detect and neutralize insider threats.

    Second, corporations must beef up their detection of malicious behavior patterns in their infrastructure. This will help them respond to threats faster and isolate the internal threat agent quickly. This response can also update the security policy to enhance the security of all endpoint devices—features normally part of endpoint detection and response (EDR) solutions.

    Third, have strong ingress (protection from incoming attacks from endpoints on the Internet) and egress (protection from exfiltration of data from the corporate network) filters. The best move: pair egress filtering, also known as DLP (data loss prevention) solutions, with endpoint security.

    Fourth, apply attribute-based access control so that if an end user is connecting using an approved device with endpoint protection implemented from an approved location (i.e., attributes), they’re given greater access compared to those accessing the Internet using non-standard devices.

    And finally, continue to use traditional protection of the endpoint itself if possible. We’re talking solutions such as strong encryption, anti-malware detection, host-based firewall, host-based intrusion detection and prevention, and remote-wiping capability.

    How do cloud providers help with endpoint security?

    TL: Your stakeholders entrust you to protect their data. So, you need to own your security plan. While major cloud providers offer various endpoint security solutions, it’s vital to think of cloud security as a shared responsibility managed by you. Your organization’s reputation is on the line. You have bottom-line responsibility for security.

    Via: https://www.pluralsight.com/

  • Six ways to improve data lake security

    Six ways to improve data lake security

    Data lakes, such as Oracle Big Data Service, represent an efficient and secure way to store all of your incoming data. Worldwide big data is projected to rise from 2.7 zettabytes to 175 zettabytes by 2025, and this means an exponentially growing number of ones and zeroes, all pouring in from an increasing number of data sources. Unlike data warehouses, which require structured and processed data, data lakes act as a single repository for raw data across numerous sources.

    What do you get when you establish a single source of truth for all your data? Having all that data in one place creates a cascading effect of benefits, starting with simplifying IT infrastructure and processes and rippling outward to workflows with end users and analysts. Streamlined and efficient, a single data lake basket makes everything from analysis to reporting faster and easier.

    There’s just one issue: all of your proverbial digital eggs are in one “data lake” basket.

    For all of the benefits of consolidation, a data lake also comes with the inherent risk of a single point of failure. Of course, in today’s IT world, it’s rare for IT departments to set anything up with a true single point of failure—backups, redundancies, and other standard failsafe techniques tend to protect enterprise data from true catastrophic failure. This is doubly so when enterprise data lives in the cloud, such as with Oracle Cloud Infrastructure, as data entrusted in the cloud rather than locally has the added benefit of trusted vendors building their entire business around keeping your data safe.

    Does that mean that your data lake comes protected from all threats out of the box? Not necessarily; as with any technology, a true assessment of security risks requires a 360-degree view of the situation. Before you jump into a data lake, consider the following six ways to secure your configuration and safeguard your data.

    Establish Governance: A data lake is built for all data. As a repository for raw and unstructured data, it can ingest just about anything from any source. But that doesn’t necessarily mean that it should. The sources you select for your data lake should be vetted for how that data will be managed, processed, and consumed. The perils of a data swamp are very real, and avoiding them depends on the quality of several things: the sources, the data from the sources, and the rules for treating that data when it is ingested. By establishing governance, it’s possible to identify things such as ownership, security rules for sensitive data, data history, source history, and more.

    Access: One of the biggest security risks involved with data lakes is related to data quality. Rather than a macro-scale problem such as an entire dataset coming from a single source, a risk can stem from individual files within the dataset, either during ingestion or after due to hacker infiltration. For example, malware can hide within a seemingly benign raw file, waiting to execute. Another possible vulnerability stems from user access—if sensitive data is not properly protected, it’s possible for unscrupulous users to access those records, possibly even modify them. These examples demonstrate the importance of establishing various levels of user access across the entire data lake. By creating strategic and strict rules for role-based access, it’s possible to minimize the risks to data, particularly sensitive data or raw data that has yet to be vetted and processed. In general, the widest access should be for data that has been confirmed to be clean, accurate, and ready for use, thus limiting the possibility of accessing a potentially damaging file or gaining inappropriate access to sensitive data.

    Use Machine Learning:Some data lake platforms come with built-in machine learning (ML) capabilities. The use of ML can significantly minimize security risks by accelerating raw data processing and categorization, particularly if used in conjunction with a data cataloging tool. By implementing this level of automation, large amounts of data can be processed for general use while also identifying red flags in raw data for further security investigation.

    Partitions and Hierarchy: When data gets ingested into a data lake, it’s important to store it in a proper partition. The general consensus is that data lakes require several standard zones to house data based on how trusted it is and how ready-to-use it is. These zones are:

    • Temporal: Where ephemeral data such as copies and streaming spools live prior to deletion.
    • Raw: Where raw data lives prior to processing. Data in this zone may also be further encrypted if it contains sensitive material.
    • Trusted: Where data that has been validated as trustworthy lives for easy access by data scientists, analysts, and other end users.
    • Refined: Where enriched and manipulated data lives, often as final outputs from tools.

    Using zones like these creates a hierarchy that, when coupled with role-based access, can help minimize the possibility of the wrong people accessing potentially sensitive or malicious data. 

    Data Lifecycle Management:Which data is constantly used by your organization? Which data hasn’t been touched in years? Data lifecycle management is the process of identifying and phasing out stale data. In a data lake environment, older stale data can be moved to a specific tier designed for efficient storage, ensuring that it is still available should it ever be needed but not taking up needed resources. A data lake powered by ML can even use automation to identify and process stale data to maximize overall efficiency. While this may not touch directly on security concerns, an efficient and well managed data lake allows it to function like a well-oiled machine rather than collapsing under the weight of its own data.

    Data Encryption:The idea of encryption being vital to data security is nothing new, and most data lake platforms come with their own methodology for data encryption. How your organization executes, of course, is critical. Regardless of which platform you use or what you decide between on premises vs, cloud, a sound data encryption strategy that works with your existing infrastructure is absolutely vital to protecting all of your data whether in motion or at rest—in particular, your sensitive data.

    Create Your Secure Data Lake

    What’s the best way to create a secure data lake? With Oracle’s family of products, a powerful data lake is just steps away. Built upon the foundation of Oracle Cloud Infrastructure, Oracle Big Data Service delivers cutting-edge data lake capabilities while integrating into premiere analytics tools and one-touch Hadoop security functions. Learn more about Oracle Big Data Service to see how easy it is to deploy a powerful cloud-based data lake in your organization—and don’t forget to subscribe to the Oracle Big Data blog to get the latest posts sent to your inbox.

    Via: https://blogs.oracle.com/

  • Top 3 cybersecurity threats and how to prevent them

    Top 3 cybersecurity threats and how to prevent them

    According to PWC research, 71% of CEOs are extremely concerned about a cyberattack. And rightfully so. Cyberattacks occur constantly, and it can feel like it’s only a matter of time before your own organization is struck by a cybersecurity breach.

    While a cybersecurity breach may feel inevitable, in reality there are steps that can be taken to greatly reduce threats. The first part of cybersecurity is understanding the many possible vectors of attack a hacker can take.

    In this post, we will discuss three different security breaches. We’ll walk through what they are and best practices that can be implemented to prevent them. Let’s start with the most common and least technological threat: social engineering.

    What is Social Engineering?

    Social engineering is a wide net that can be used to describe numerous different scams and hacks. The basic premise though is manipulating members of an organization to steal confidential data and gain unauthorized access. One of the most common social engineering methods is phishing. Another example is impersonation, where a hacker will claim to be an employee to obtain information. Let’s first take a look at phishing.

    What is Phishing?

    Phishing is when a hacker sends an email that appears legitimate, but is not. The email is the bait, the hacker is the fisherman, and you are the fish. The purpose of a phishing attack is to obtain data by claiming to be a person or organization of authority. Phishing emails appeal to the user’s sense of urgency, or some other psychological aspect that would get someone to click the link. Let’s look at a quick example.

    Let’s say you received an email from the “Human Resources Department”. In the email, it says that your badge is going to expire tomorrow, and you must click the link in the email to reserve a badge replacement time. If you do not reserve a spot, your badge will expire and you will no longer be able to come to work.

    This email appeals to our sense of urgency. We don’t want to not be able to access our workplace. It also appeals to our sense of authority — i.e our HR department is a legitimate source. Assuming you unfortunately click the link, you will be forwarded to a fake website that would ask you to put in your email and password to reserve a badge replacement time. Now the hacker has your username and password and can do unprecedented amounts of damage to you and your organization.

    How to Prevent a Phishing Attack

    The best way to prevent a phishing attack is to look for red flags. Make sure all emails that are coming from outside your organization are sequestered into a separate email folder.

    Next, advise your IT staff to set up phishing emails to send to employees so they can practice what to look for when it comes to phishing attempts. Oftentimes, phishing emails will have misspelled words or strange wording, as if the person who wrote it doesn’t speak English.

    Phishing attempts will always appeal to the employee’s sense of urgency to get them to click the link. E.G, it will say something along the lines of, “you will no longer be able to work here if you don’t update your address on this link.” Remember: Stop and think before clicking that link.

    What is Impersonation?

    The next form of social engineering is impersonation. A hacker will claim to be an employee of the organization and try to get their password reset. The hacker will often trawl logs that leak onto the website. They can use this to obtain information they wouldn’t otherwise have. Then they call the IT department and give information that will seem credible such as employee numbers, date of birth, and other information.

    How can Impersonation Attacks be Prevented?

    Impersonation attacks can be prevented by well-trained employees who vigorously follow procedural compliance. For example, check the phone number that the number is coming from. If it is not a recognized number, that is a red flag. Ask the “employee” who their manager is and who their co-workers are. Ask them a little bit about their job. If they fumble, then that is a bad sign.

    When talking to people, it is human nature to be as helpful and assistive as possible; this is a crucial mistake when dealing with IT security. If you are suspicious, ask followup questions or simply hang up the phone and inform your manager of a potential cybersecurity attack.

    Impersonation is one of the more insidious aspects of cybersecurity, because it is so personal. Next, let’s talk about how ransomware can cripple your organization, and what steps can be taken to prevent it.

    What is Ransomware?

    Ransomware is a type of virus that threatens to publish private data or withhold critical data until a certain demand is met. Typically the demand is monetary compensation in the form of cryptocurrency.

    It is a sad reality that ransomware attacks are becoming commonplace. In 2021 alone, there have been dozens of ransomware attacks, ranging from the Buffalo Public School System to Colonial Pipeline Systems. More often than not, the organizations have to pay the criminals the ransom to get their data back.

    Protecting against a ransomware attack after it has already occurred is sort of like locking the barn door after the horses ran away. Once the hackers have your data, they have your data. However, there are numerous steps that can be taken to harden your security infrastructure to prevent these travesties from occurring

    Endpoint Hardening Can Prevent Against Ransomware

    One of the best ways to prevent ransomware is to ensure your software engineers are taking a proactive approach to security when designing a system. This is called Security by Design.

    One such method of preventing ransomware is to harden your endpoints. Think of an endpoint as an access point to your application. Whether it is via a login screen, or a URL for a REST endpoint. Make sure that all data is sanitized so that hackers cannot send malicious data to the endpoints. This is often referred to as SQL injection or Cross-Site request Forgery.

    Another good way to harden your endpoint is to disable Cross-origin Resource Sharing (CORS). This will ensure that only your app is only communicating with an authenticated server. Please note, though, there are some instances we want CORS enabled. For example, Google Fonts require CORS.

    Lastly, two-factor authentication should be enabled on all devices. This will make it much more difficult for a hacker to steal somebody’s device and crack the password.

    Keeping Software Up to Date is Crucial

    Another important strategy to prevent ransomware is to keep all software and frameworks up to date. For example, if your team uses Spring Boot for their Java framework, make sure it is on the latest version. That goes for all other frameworks such as React and Angular.

    The organizations responsible for maintaining these frameworks are constantly finding security vulnerabilities in their code and updating them accordingly. If you do not update the code, it is only a matter of time before a hacker exploits it.

    While many hackers utilize proactive approaches such as social engineering and ransomware, often all they have to do is wait for a vulnerable security misconfiguration. Let’s walk through that, because it is becoming such a serious issue.

    Beware of Cloud Security Misconfiguration

    In every case of a cloud hack, it has been traced back to a misconfiguration. Google, AWS, and Microsoft go through great length to ensure their data storage tools are uncompromisable. In the cloud world, however, there is a shared responsibility model that determines what is the duty of the cloud provider and what is the responsibility of the user. Each cloud provider has some version of the model, but the AWS version looks like this:

    Notice that the customer is responsible for a wide swath of duties, ranging from their data, to access and management, all the way to firewall configuration. These are where hacks most often occur. Let’s talk specifically about S3 buckets, AWS’s flagship data storage model.

    What is an S3 bucket?

    For the uninitiated, think of an S3 bucket as a scalable document-based database. Any data imaginable can be stored in these buckets, and it is completely scalable to meet your needs. It’s accessible via endpoints or a user interface on the AWS console.

    Why are S3 Buckets Cybersecurity Threats?

    In June of 2017, a hacker revealed 198 million voter records from a misconfigured S3 bucket. Suffice to say, that is not good. It can be traced back to an S3 bucket being misconfigured to public accessibility. If that is not a wakeup call to cybersecurity experts, I don’t know what is!

    S3 buckets are created secure by default. In other words, they do not have access to the internet. However, configuring S3 endpoints and determining which ones should have access to the internet can be challenging. It is a process rife with misconfiguration, and often, AWS engineers will accidentally give an S3 bucket access to the internet.

    Once an S3 bucket has this access, any hacker can hit that endpoint and retrieve huge amounts of data. For example, Grayhat Warfare can be used to find public S3 buckets. Then, they can ransom it back to the organization, sell it to a third party or blackmail somebody.

    How to Prevent Misconfiguration

    The easiest way to eliminate this threat is to be very careful when configuring the S3 buckets. Have more than one person verify the configurations before putting it out into the wild. Only allow users who are certified in the technology access to the cloud console. Test engineers can also create integration tests that ping the bucket to verify it does not have access to the internet. If it does, the test fails and the software engineering department is notified.

    This is not exclusive to Amazon buckets. Azure and Google buckets can potentially be misconfigured in the same way.

    Final Thoughts

    In this post, we talked about three major vectors of attack: social engineering, ransomware, and cloud security misconfiguration. Each one of these are very different and diverse. Also, each involves different employees in the organization. Social engineering works by tricking people, ransomware is exploiting security bugs, and cloud security hacks exploit configuration errors.

    It is important to remember that Cybersecurity is not relegated to one particular team. It is everyone’s responsibility. Everyone, from the CEO down, should have some level of cybersecurity awareness training.

    Via: https://www.cbtnuggets.com/